[systemd-devel] Minimal builds

[Lennart Poettering]

On Wed, 20.06.12 15:56, William Hubbs (w.d.hubbs at gmail.com) wrote:

> On Wed, Jun 20, 2012 at 06:22:49PM +0200, Lennart Poettering wrote:
> > Heya,
> > 
> > regarding the whole discussion on minimal builds and people wanting to
> > pick specific parts of the systemd build leaving out others, beyond what
> > the configure switches offer: Here are some guidelines how we recommend
> > people to do this:
> > 
> > http://freedesktop.org/wiki/Software/systemd/MinimalBuilds
> > 
> > From our side this should be enough to settle the discussion.
> 
> It isn't for us, because, for example, if I use option 1, I have to do
> the opposite of the second half of it. Our pm installs everything in the
> place pointed to by DESTDIR, then I have to manually remove the things I
> don't need. As was pointed out in a thread earlier, this is very
> error-prone and definitely could lead to issues.

Hmm? This really appears to be a broken package manager. Sorry, but I am
not going to work around the limitations of downstream package managers
in upstream packages if everybody else gets this right.

> Another thing to think about from our side is, although the main
> components compile quickly on a pc, how long would it take to compile
> everything on an ARM-based machine for example? I have no idea, so it
> could end up being really annoying to users of that platform  for us to
> compile all of the main components and turn around and remove most of
> them.

We don't optimize for build time performance, we optimize for runtime
performance. Source based distributions made the deliberate choice to
rebuild everything all the time. They made that choice and they need to
accept to pay the price for it: things are slower than when they just
did "rpm -i" on a binary package...

Lennart

-- 
Lennart Poettering - Red Hat, Inc.