On 30-03-2009 18:43:14 +0100, mephx wrote:
> Besides re-writing eselect in plain C the new implementation would be
> as follows:

I don't think C is a necessity (even though it has my preference), and
might interfere with some requirements, as Donnie already pointed out.

> Every ebuild with SLOT != 0 would create it's own "module" in a
> per-system DB (similar to /var/db) allowing the module listing and
> switching easy. This implies some coding on portage and a few parameter
> tweaking on each "modulable" ebuild.
> The "module" creation would be automatic and therefore created upon a
> successful emerge.
> Another per-user DB would be maintained and read upon each login for
> environment switching (adding a few lines on /etc/bash.rc or similar).
> The per-user DB would also allow various profiles per user and fast
> switching between them.

In this approach, would it be possible to just use the (existing) vdb?
Tools like portage-utils show that you can search through its contents
quickly enough not to even require an index actually.  And if the
package manager is involved anyway, it can simply write those extra bits
you need in the vdb as well, as separate entries.

Big question would be, what.  Like, how would a thing like gcc-config or
binutils-config be implemented like that.  How would be the management
of different versions of the scripts that handle the actual switching
and stuff.


-- 
Fabian Groffen
Gentoo on a different level