On Tue, 2003-10-28 at 19:02, [EMAIL PROTECTED] wrote: > I have a script I put together that will 'emerge' packages into an > alternate root using portage. My goal was a machine 'image' that I > could stick in an embedded device, and if upgrades were needed I would > upgrade the 'image' not individual packages. > At the smallest so far, i put busybox+glibc+kernel in 50 megs(i know > that's huge i compiled in locales and other junk), but right now I'm > working on building a uclibc toolchain. And I should have that > finished in about a week.
I would be very interested in seeing how you went about doing this. As I understand you use a host gentoo installation to "emerge" packages into a clean root. What I wonder is what that root contains? Do you start with a skeleton? If so what? and finally do you use the bin package feature portage provides to carry this out? My eventual goal as I stated before is to have as lean/clean server enviornment as possible and as a secondary consequence try to make bootable CDs with custom selectable tools/apps. Regarding the -doc flag... I wonder how many packages support it. Cheers, Vano. -- [EMAIL PROTECTED] mailing list
