Date: Fri, 22 Jul 2005 15:14:17 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: Jeremie Le Hen <jeremie@le-hen.org>, Ken Smith <kensmith@cse.Buffalo.EDU> Cc: freebsd-current@freebsd.org Subject: Re: HEADS-UP: New shared library versions coming soon Message-ID: <p0623096ebf06f39b6295@[128.113.24.47]> In-Reply-To: <20050722174802.GS39292@obiwan.tataz.chchile.org> References: <1121952594.68685.27.camel@opus.cse.buffalo.edu> <20050722174802.GS39292@obiwan.tataz.chchile.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 7:48 PM +0200 7/22/05, Jeremie Le Hen wrote:
>Hi Ken, hi all,
>
>> It will take a while for the fallout from this version bump to
> > propagate. People who cvsup/rebuild existing systems should not
> > be impacted immediately - you will still have the older library
> > versions present on your systems. However it will take time for
> > the pre-built packages provided by the portmgr folks to be rebuilt,
> > loaded onto the FTP servers, and propagate out to the mirrors.
>
>I know that FreeBSD is still lacking a solution to remove old
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>librairies, but I would like to know the actual recommended way
>to remove old libraries. ... But I would like to hear what
>others do to achieve this. In short, I'm looking for a
>neat solution.
^^^^^^^^^^^^^^^
If someone *had* a neat solution, one which everyone agreed was a
neat, workable, reliable solution, then FreeBSD would not be lacking
a solution... :-)
I have my own way of dealing with this, and I am comfortable with
it, but I would not call it neat. It works "well enough" for me,
but might not work for others. I only have four or five machines I
have to worry about, so I can get by with a messy solution.
--
Garance Alistair Drosehn = gad@gilead.netel.rpi.edu
Senior Systems Programmer or gad@freebsd.org
Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p0623096ebf06f39b6295>