All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Stanislav Brabec <sbrabec@suse.cz>
Cc: util-linux@vger.kernel.org
Subject: Re: util-linux and distro bootstrap, dependencies and build cycles
Date: Mon, 11 Aug 2014 21:17:02 -0400	[thread overview]
Message-ID: <1549603.ZWLTNRFnAF@vapier> (raw)
In-Reply-To: <1407768431.5984.23.camel@oct.suse.cz>

[-- Attachment #1: Type: text/plain, Size: 692 bytes --]

On Mon 11 Aug 2014 16:47:11 Stanislav Brabec wrote:
> Solution 1:
> 
> Modify make system by adding:
> --enable-build-stage-1: Distro bootstrap stage 1: Build only code
>     without systemd and python dependencies.
> --enable-build-stage-2: Distro bootstrap stage 2: Build code with
>     systemd dependencies (even if they are optional). Use installed
>     instances of libmount, libblkid, libsmartcols and libuuidd, do not
>     build them in-tree.
> --enable-build-stage-3: Distro bootstrap stage 3: Build python-libmount
>     only. Use installed instance of libmount, do not build them in-tree.

how is this any different from just passing --without-{udev,python} ?
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-08-12  1:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-11 14:47 util-linux and distro bootstrap, dependencies and build cycles Stanislav Brabec
2014-08-12  1:17 ` Mike Frysinger [this message]
2014-08-12 20:15   ` Stanislav Brabec
2014-08-12 23:49     ` Mike Frysinger
2014-08-13  9:26     ` Karel Zak
2014-08-12  9:39 ` Karel Zak
2014-08-12 20:15   ` Stanislav Brabec
2014-08-13 10:17     ` Karel Zak
2014-08-13 14:53       ` Stanislav Brabec
2014-08-13 17:25         ` Linda Walsh
2014-08-14  8:48         ` Karel Zak
2014-08-14 16:02           ` Stanislav Brabec

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1549603.ZWLTNRFnAF@vapier \
    --to=vapier@gentoo.org \
    --cc=sbrabec@suse.cz \
    --cc=util-linux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.