Peter Jeremy wrote:
On 2007-May-19 16:21:49 -0700, Doug Barton <[EMAIL PROTECTED]> wrote:
I still feel that the only safe way to do this is to find the union of
'ldconfig -r' and 'pkg_info -L' and save those files, and those files only.
That should be intersection, not union.
Yeah, that's
On 2007-May-19 16:21:49 -0700, Doug Barton <[EMAIL PROTECTED]> wrote:
> 1. Before deinstall, save shared libs in /usr/local/lib/compat/pkg
> 2. After install, remove anything from /usr/local/lib/compat/pkg with the
> same name as something installed by the new port.
One possible gotcha with blind
Michel Talon wrote:
Not completely because some programs install shared libraries in very
non standard places, notably perl installs perl.so like this:
/usr/local/lib/perl5/5.8.8/mach/CORE/libperl.so
or mozilla installs mozilla libs in another strange place. And there are
other ports which make
On Sat, May 19, 2007 at 07:47:30AM +1000, Peter Jeremy wrote:
> On 2007-May-18 17:50:58 +1000, Peter Jeremy <[EMAIL PROTECTED]> wrote:
> >Ideally, you also need some way to identify (and remove) old .so files
> >that are no longer referenced by anything. This is not as easy
> >because there's no r
On 2007-May-18 17:50:58 +1000, Peter Jeremy <[EMAIL PROTECTED]> wrote:
>Ideally, you also need some way to identify (and remove) old .so files
>that are no longer referenced by anything. This is not as easy
>because there's no record of what ports use what .so's (and no way to
>track apps outside
Doug Barton píše v pá 18. 05. 2007 v 12:29 -0700:
> Pav Lucistnik wrote:
> > Doug Barton píše v c(t 17. 05. 2007 v 13:06 -0700:
> >
> >> What might
> >> be useful in this regard is if someone were to start a new thread
> >> describing exactly what the desired behavior is, and ideally to
> >> in
Pav Lucistnik wrote:
Doug Barton píe v c(t 17. 05. 2007 v 13:06 -0700:
What might
be useful in this regard is if someone were to start a new thread
describing exactly what the desired behavior is, and ideally to
include a description of how portupgrade does it now.
Just before old package
On 5/18/07, Robert Huff <[EMAIL PROTECTED]> wrote:
When in need of emergency disk space, my first trick is to
flush /usr/ports/distfiles and /usr/obj.
If that's not enough, I empty /usr/local/lib/compat/pkg. About
one time in twenty I discover something important was depend
RW writes:
> > > The last part seems to be the catch here. How about providing a
> > > tool that scans all binaries in the standard locations for what
> > > libs they depend on, and also allows the user/admin to specify
> > > the paths to binaries that he installed on his own, then outpu
Benjamin Lutz píše v pá 18. 05. 2007 v 14:09 +0200:
> On Friday 18 May 2007 09:50, Peter Jeremy wrote:
> > On 2007-May-17 23:31:57 +0200, Pav Lucistnik <[EMAIL PROTECTED]> wrote:
> > >Just before old package deinstall, scan the list of files installed
> > > by old port (pkg_info -g). Match .so.X fi
RW píše v pá 18. 05. 2007 v 15:47 +0100:
> One thing that does worry me a bit, is the possibility that a new port
> install might find these one of these orphaned libraries, and fail to
> install a LIB_DEPENDS port.
Can't happen. Ports infrastructure does not check lib/compat/pkg when
satisfying
On Fri, 18 May 2007 08:38:40 -0400
Robert Huff <[EMAIL PROTECTED]> wrote:
> Benjamin Lutz writes:
>
> > The last part seems to be the catch here. How about providing a
> > tool that scans all binaries in the standard locations for what
> > libs they depend on, and also allows the user/admin to
Benjamin Lutz wrote:
> > Benjamin Lutz writes:
> > > The last part seems to be the catch here. How about providing a
> > > tool that scans all binaries in the standard locations for what
> > > libs they depend on, and also allows the user/admin to specify
> > > the paths to binaries that he i
On Friday 18 May 2007 14:38, Robert Huff wrote:
> Benjamin Lutz writes:
> > The last part seems to be the catch here. How about providing a
> > tool that scans all binaries in the standard locations for what
> > libs they depend on, and also allows the user/admin to specify
> > the paths to bin
Benjamin Lutz writes:
> The last part seems to be the catch here. How about providing a
> tool that scans all binaries in the standard locations for what
> libs they depend on, and also allows the user/admin to specify
> the paths to binaries that he installed on his own, then outputs
> a lis
On Friday 18 May 2007 09:50, Peter Jeremy wrote:
> On 2007-May-17 23:31:57 +0200, Pav Lucistnik <[EMAIL PROTECTED]> wrote:
> >Just before old package deinstall, scan the list of files installed
> > by old port (pkg_info -g). Match .so.X files under PREFIX/lib and
> > any ldconfig'ed paths 1*), copy
On 2007-May-17 23:31:57 +0200, Pav Lucistnik <[EMAIL PROTECTED]> wrote:
>Just before old package deinstall, scan the list of files installed by
>old port (pkg_info -g). Match .so.X files under PREFIX/lib and any
>ldconfig'ed paths 1*), copy them away to /usr/local/lib/compat/pkg.
>
>After installat
17 matches
Mail list logo
