1 |
On Thu, Jul 15, 2010 at 07:28:40PM +0200, Markus Hauschild wrote: |
2 |
> On Thu, Jul 15, 2010 at 10:49 AM, Mike Auty <ikelos@g.o> wrote: |
3 |
> > Ideally, these calls should either adhere to FEATURES="-preserve-libs", |
4 |
> > or there should be a tool that can identify which files portage has |
5 |
> > preserved, and allow easy rebuilding of dependent packages, and removal. |
6 |
> > At the moment, I'm having to manually grep ebuilds, ls the libraries |
7 |
> > and run revdep-rebuild over them one at a time... |
8 |
> |
9 |
> Such a tool which can at least identify files that remain on the |
10 |
> system from preserved-libs or similar would be really useful in my |
11 |
> opinion! |
12 |
|
13 |
What if preserve_old_libs did the following: |
14 |
|
15 |
mv ${oldlib} ${oldlib}.preserved |
16 |
ln -s ${oldlib}.preserved ${oldlib} |
17 |
|
18 |
Cons: 2 files to delete once you're done revdep-rebuilding |
19 |
|
20 |
Pros: Easy to tell at a glance which libs are the preserved libs. |
21 |
|
22 |
-- |
23 |
Jim Ramsay |