From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 11 Jun 2008 17:30:20 +0200 From: Enrico Weigelt To: 9fans@9fans.net Message-ID: <20080611153020.GE402@nibiru.local> References: <20080611124038.GA3004@nibiru.local> <20080611132853.E4B821E8C1F@holo.morphisms.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080611132853.E4B821E8C1F@holo.morphisms.net> User-Agent: Mutt/1.4.1i Subject: Re: [9fans] Modularizing plan9port Topicbox-Message-UUID: baa90d30-ead3-11e9-9d60-3106f5b1d025 * Russ Cox wrote: Hi, > Ask yourself whether you're doing this because it would > actually make your life easier or because of some It *does* make my life easier! I'm not just using it for personal stuff, but for lots of highly customized production systems, where careful maintenance is very important. Disk space is not the issue, but the amount of code to be maintained (source and binary). So the target systems *always* should only contain exactly what's needed - nothing more. > pre-conceived notion that software packaging should be complex. Actually, I want to make it simpler. You probably can't see this since you don't know what happens behind the scenes at my site ;-P One essential constraint is, that everything's built through an sysroot'ed cross-toolchain. Right after compile several checks run on the output, packages are then trimmed-down (eg. removing all build-time stuff) and then it goes to the testing system. Only after the whole pipe ran through properly, the binary package is committed to the production systems. > There's no need to fiddle with the build structure: > you could still require the whole tree to build things > and then just split up the post-build tree. The current approach already fails with crosscompiling. I *can not* use the in-tree built mk for further building and I *must* make sure that imports are strictly coming from within sysroot. > Then you don't have to worry about rewriting Makefiles > or adding your own configure scripts or other horrors. > I certainly won't take any of that back into the main tree. You shouldn't generally declare this approach as horror, just because autoconf is a horrible example. cu -- ---------------------------------------------------------------------- Enrico Weigelt, metux IT service -- http://www.metux.de/ cellphone: +49 174 7066481 email: info@metux.de skype: nekrad666 ---------------------------------------------------------------------- Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme ----------------------------------------------------------------------