perhaps something like `catalyst --build-seed <ROOT>` ... then it'll just run something like `env USE="-* build" ROOT=<ROOT> emerge --nodeps <packagelist>` the packagelist can probably be hardcoded into /usr/lib/catalyst/modules/seed.py as this: virtual/os-headers sys-devel/binutils sys-devel/gcc-config sys-devel/gcc sys-libs/glibc app-arch/bzip2 app-arch/gzip app-arch/tar app-shells/bash net-misc/rsync sys-apps/baselayout sys-apps/coreutils sys-apps/cronbase sys-apps/debianutils sys-apps/gawk sys-apps/grep sys-apps/portage sys-apps/sed sys-apps/shadow sys-devel/distcc
actually, you can take out cronbase and shadow from that list and add sys-apps/texinfo
and, as i get used to actually using catalyst, perhaps it'd be even easier if the stage1 stuff was touched up to handle this ... in reality, a seed is just a basic stage1 ... perhaps it would just emerge all the packages (like in stage1) with ROOT set to some value, tar up the result, and save it as a seed ...
actually, looks like the embedded target can do just this already. Check out (in CVS) examples/embedded/sys.spec - you will see what I mean when you see it ;)
