If I were using exherbo as a base for an embedded OS (which, BTW, I think is a retarded idea), I'd probably build binary packages first, and then installed them into rootfs of the target. Of course, you'd still have to clean that up later on, since exheres install things like man pages, includes, .pc files, and tons of other crap, absolutely needed on developer desktop system, but just a dead weight on an embedded.
Like I said - idea is a retarded one. Use one of dedicated build systems, which have all you need to have a great cross-compile-capable embedded distro. My personal favorite, the simple man that I am, is buildroot. However, things like openembedded, openwrt, snapgear, and whole gamut of others will work just as well. On 11/02/11 17:01, Doc Holliday wrote:
Theoretically speaking -- and I am just throwing out a crazy idear out there -- but theoretically speaking, if pkg A is a build only dep for pkg B, then once pkg B is built and installed, pkg A can be uninstalled from the system. This would of course require all exheres to correctly list packages in build and build+run deps. I was just thinking if I were to use Exherbo in an embedded system with very limited space, I could throw in uClibc or dietlibc, remove build only deps (gcc alone takes up 100+MB) and be done with it. Are there other things I am not thinking of? -Doc
-- Ilya A. Volynets-Evenbakh http://www.total-knowledge.com _______________________________________________ Exherbo-dev mailing list [email protected] http://lists.exherbo.org/mailman/listinfo/exherbo-dev
