tvali wrote: > So, if portage would be looked as lists and operations with lists > (calculating dependencies of package would be operation with list of > that package and list of all - portage tree -, then); building tools > [shell commands] for creating those lists and tools for operations > with those lists and leaving "emerge" tool just a handy interface to > command them would be imho great.
What about something along these lines... Add the capability for emerge to take a category as an argument, emerge www-apps for example, and emerge all packages within that category. Optionally make it so this will only work on categories within PORTDIR_OVERLAY, or create a new type of overlay, LIST_OVERLAY. Then the user can create overlays with their own category names and symlink in the package directories they want from the real portage tree. -- [email protected] mailing list
