Hi! On Sat, 2011-08-13 at 13:28:36 +0200, Andreas Barth wrote: > During bootstraping a new architecture, there are sometimes ugly > build-dependency-loops (usually involving generating documentation > for the core build utilities means you need to have the architecture > already available; same with graphical tools). During DebConf, Wookey > had a talk which lead to us discussing some ideas how to support that. > Most packages are not affected at all by that, and current behaviour > isn't changing as long as package source files are not changed. > > Below is my summary of the ideas - names et all are of course just > names and up to be changed. Advantage of this schema is that most > implementation is just package-local - the maintainer knows which > minimal versions his source package could produce, and just annotates > them. Coordination between different packages is not needed so much > anymore, and we could try to bring the build-dependencies more into a > tree-shape. Please see e.g. > http://meetings-archive.debian.net/pub/debian-meetings/2011/debconf11/low/745_Bootstrapable_Debian.ogv > for the talk.
During the Extremadura Embedded meeting in 2006 we discussed too these things, and I came up with the following proposals, which should be generic enough not only for bootstrapping but also for embedded type of reduced builds: <http://www.hadrons.org/~guillem/debian/docs/embedded.proposal> regards, guillem -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110813144839.ga5...@gaara.hadrons.org
