Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 07 May 2007 15:35:48 -0500
From:      "Jeremy Messenger" <mezz7@cox.net>
To:        "Kris Kennaway" <kris@obsecurity.org>
Cc:        ports@freebsd.org, Doug Barton <dougb@freebsd.org>
Subject:   Re: HEADS UP: xorg upgrade plans
Message-ID:  <op.try4tyhd9aq2h7@mezz.mezzweb.com>
In-Reply-To: <20070507201448.GA52651@xor.obsecurity.org>
References:  <20070502193159.GB42482@xor.obsecurity.org> <463F7236.4080108@FreeBSD.org> <20070507184231.GA50639@xor.obsecurity.org> <op.try3lgvv9aq2h7@mezz.mezzweb.com> <20070507201448.GA52651@xor.obsecurity.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 07 May 2007 15:14:48 -0500, Kris Kennaway <kris@obsecurity.org> =
 =

wrote:

> On Mon, May 07, 2007 at 03:09:06PM -0500, Jeremy Messenger wrote:
>
>> >No, at a minimum I am not comfortable recommending its use until it
>> >saves old shared libraries across updates (I sent you email about th=
is
>> >a while ago), which is a vital safety and robustness mechanism.
>>
>> I am one of people that dislike this and it is not required to get bu=
ild
>> function. ;-) I think this option should be disable by default, becau=
se
>> put stuff in lib/compat/pkg hides the problems. Also:
>
> No, it is required when dealing with shared library bumps (which
> happen about once a week).  Otherwise all of the installed ports using=

> the library break if the new library build fails.  Talk to Brooks
> about how annoying this is with e.g. gettext.

portmaster has a feature to backup the old package before the upgrade. I=
  =

think it is better than put in lib/compat/pkg. When I used portupgrade a=
nd  =

I always have lib/compat/pkg disabled until I switched to portmaster. I =
 =

never have that problem when ports tree is flexible enough to downgrade =
 =

and wait until someone fix it.

Cheers,
Mezz

>> http://www.freebsd.org/gnome/docs/faq2.html#q2
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> [...]
>> Prevent two versions of the same library.
>>
>> A common source of build failures is the existence of multiple versio=
ns  =

>> of
>> the same library. This can happen if you have two different versions =
of  =

>> a
>> port installed, or can even happen through normal portupgrade use. Yo=
u  =

>> can
>> back up the libraries in /usr/local/lib/compat/pkg and remove them, a=
nd
>> then run portupgrade -u -rf pkg-config. This will force a rebuild of =
all
>> GNOME-related apps (and a fair number of other apps) without retainin=
g  =

>> old
>> versions of libraries in /usr/local/lib/compat/pkg.
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> I dispute the correctness of this entry.  The old libraries in
> lib/compat/pkg are not linked to directly by new builds.  The only
> situation in which something might end up being linked to 2 versions
> of the library is if it pulls in a library dependency from an existing=

> port that is still linked to the old library.  In this situation the
> build would be broken with or without lib/compat/pkg (in the latter
> case, you have an installed port linked to a library that is entirely
> missing, so that port will be nonfunctional).
>
> Kris


-- =

mezz7@cox.net  -  mezz@FreeBSD.org
FreeBSD GNOME Team  -  FreeBSD Multimedia Hat (ports, not src)
http://www.FreeBSD.org/gnome/  -  gnome@FreeBSD.org
http://wiki.freebsd.org/multimedia  -  multimedia@FreeBSD.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.try4tyhd9aq2h7>