Ok, those would be your goals for the non-bootstrapping fork.
Aside from obvious goals (like, "cleaner, simpler, cooler")
my vague idea is:
I want to make it much easier to audit installations and to automate
package dependency handling. I want to make it easier to construct
multiple user environments (different mixes of package versions) on a
single system (as for multiple users, development environments, or
test environments). I'd like to use the build tools to solve the
problem described as "RPM hell" (s/RPM/<your favorite package
system>/). Higher-level-still shared library support seems to be
needed.
And, of course, I'd like the auditing features to tie into distributed
revision control :-)
-t
