Your idea is a step in the right direction, but the ideal config would have a top level portage.git with sub-modules for each category, as well as for eclass, licenses, profiles and scripts. Each category.git should have sub-modules for each package therein.
Within the profiles.git it *might* be reasonable for each directory in arch/ also to be a sub-modules. Or not. That should be dicussed. And the bureaucracy should be minimal. Adding, changing or removing a submodule from its parent repo should only require a call for consensus among the devs, and not be pushed through a small set of devs on some given team. It may also be useful for the process which generates metadata/ to push out to a repo, too, just before syncing out to the rsync mirrors. Having each package in its own repo is a great idea. But a simple recursive git pull to update the whole thing is highly desireable. Git submodules fit the bill perfectly. This would require re-doing the cvs→git conversion, but it’d be worth it. -JimC -- James Cloos <cl...@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
