From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Proposed util-linux split
Date: Tue, 26 Feb 2013 15:49:15 -0300 [thread overview]
Message-ID: <512D03AB.3060508@zacarias.com.ar> (raw)
In-Reply-To: <20130226194054.0ab6cb97@skate>
On 02/26/2013 03:40 PM, Thomas Petazzoni wrote:
> I just checked, and PAM is only needed when login-utils is enabled.
>
> Also, 2.22 has apparently moved to a non-recursive usage of automake,
> which should make the build much, much faster.
Yes, we loose util-linux login for non-pam installations.
It's the upstream policy, everyone should have PAM.
On a personal level i don't care really, for the smallest login there's
busybox.
Yes, the build is faster too, however excluding components isn't good on
the non-recursive usage of automake, we'd just have to use good'ol rm in
a POST_BUILD hook unfortunately.
Regards.
next prev parent reply other threads:[~2013-02-26 18:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 10:53 [Buildroot] Proposed util-linux split Gustavo Zacarias
2013-02-26 18:33 ` Thomas Petazzoni
2013-02-26 18:40 ` Thomas Petazzoni
2013-02-26 18:49 ` Gustavo Zacarias [this message]
2013-02-26 18:41 ` Gustavo Zacarias
2013-02-26 19:03 ` Thomas Petazzoni
2013-02-26 19:07 ` Gustavo Zacarias
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=512D03AB.3060508@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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.