On 18:43 Mon 30 Mar     , mephx wrote:
> Besides re-writing eselect in plain C the new implementation would be as
> follows:
> 
> 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.
> 
> Would be glad to hear some comments from other gentoo/list users.

What you'll find with C only is that most of our devs won't be able to 
write modules for their own packages because they only know bash and 
maybe some python. A core in C might work, a la openrc, provided you do 
a bit of profiling to show where the holdup is and why it can't be fixed 
in a higher-level language.

-- 
Thanks,
Donnie

Donnie Berkholz
Admin, Summer of Code
Gentoo Linux
Blog: http://dberkholz.wordpress.com