On 02/10/14 09:41, Martin Lucina wrote:
> Looks like we'll be able to discuss this in London in November, I got
> myself tickets to operatingsystems.io on a whim -- hopefully half of the
> talks won't^H^H^H^H^H*will* be over my head :-)

Cool, see you there!  Hope you'll also be attending the rump kernel 
hackathon the day after.

> In my experience all build systems tend to eventually devolve into an
> unmaintainable mess internally, and said mess then requires $INTOXICANT to
> tackle.

This build system required that from the start.  buildrump.sh is 
probably around the fifth attempt (not all of them mine) to automate 
rump kernel builds for non-NetBSD targets.  IIRC the first one (from 
2007) was not very convenient, and contained bits like "then you get an 
error, just copypaste the link line and edit it slightly before 
re-running it".  At least there has been progress from the user perspective.

> What's nice about buildrump.sh is that the external user interface is
> so straightforward.  As a counter-example, I briefly contemplated building
> Firefox OS for my Nexus 7 tablet. Then I went and actually looked at the
> ~20 pages of instructions on the mozilla.org Wiki and just gave up in order
> to preserve my sanity.

buildrump.sh is simple to use at first, because the goal has been that 
if you want to try things out in userspace against the default host 
compiler, everything should work if you only type "./buildrump.sh".  If 
you look at build.sh in NetBSD, you might see where that quest for 
simplicity is coming from.  Long instructions for doing standard tasks 
always strike me as laziness which ruins the whole experience -- like 
you'd host a fancy dinner party and outsource the peeling of the 
potatoes in Sole Saint-Malo to the diners.

When I look at how buildrump.sh is used in rumprun-*, which require 
special handling, I cringe in horror and don't understand half of what's 
going on ;)

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
rumpkernel-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rumpkernel-users

Reply via email to