Looks like my first mail disappeared somehow, lets try again:

On Sat, 14 Jun 2008 22:55:23 -0500
"Lucian Poston" <lucianposton@...> wrote:

> I put the new RevdepSet module in a separate file. Should I instead
> include this in one of the existing files? I couldn't find a clear
> description of the purpose of the set classes within each file, so I
> simply placed it in a new one. Also, did anyone have a more succinct,
> descriptive name suggestion for the set already in mind?

For the purpose of SoC it's better to keep it in a separate file,
though for deployment it's probably going to be integrated into
sets/libs.py. As for name, the old prototype was named
MissingLibraryConsumerSet (mainly due to inheriting from
LibraryConsumerSet, which you might also be interested in).

> My plan over the next few days is to build a list of "needed"
> libraries (either through dbapi or my own implementation similar to
> linkmap), a list of installed libraries (I'm still unsure of the best
> way to build this list.  Simply searching through lib directories
> perhaps?), and comparing the two lists to find which are missing.  The
> packages are already associated with the libraries in var/db/pkg, so
> that shouldn't be a problem.  I'll see how that works and go from
> there.

Sounds like a job for linkmap.findProviders(), but might be an idea to
implement multiple solutions for comparison/testing purposes
(see sets/security.py for one way to do that).

> Are there any future plans to integrate the concept of recompiling
> necessary binaries against newly updated libraries when upgrading
> through emerge? Or is it more likely to stay as is with preserved-lib
> functionality? I was just wondering about the futility of this whole
> project in the future. :)

Well, the only thing I'm somewhat planning atm is to (optionally)
automatically rebuild certain sets after an emerge session, but that's
just a plan for now and definitely won't happen before SoC is over.
Other than that we'll have to see how preserve-libs works out in
practice, but I don't expect it to go away that soon.
Btw, if you're worried that preserve-libs makes your project redundant,
it won't. It is supposed to reduce the need for it, but as it's
optional and only limited in scope there will always be a need for
revdep-rebuild functionality.

> Should emerge revdep-rebuild rebuild the packages that are compiled
> against preserved libraries? I assume no, since that functionality is
> already present with preserved-libs, but I wanted to be sure.

Better to not include preserved libs. Would be trivial to create a
wrapper set to include both individual sets if necessary.

Marius

-- 
Public Key at http://www.genone.de/info/gpg-key.pub

In the beginning, there was nothing. And God said, 'Let there be
Light.' And there was still nothing, but you could see a bit better.
-- 
gentoo-soc@g.o mailing list