Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] uclibc-ng: enable fts in default config file.
Date: Fri, 13 Oct 2017 16:59:27 +0000	[thread overview]
Message-ID: <1507913966.3810.38.camel@synopsys.com> (raw)
In-Reply-To: <20171012180819.GI7617@waldemar-brodkorb.de>

Hi Thomas,

On Thu, 2017-10-12 at 20:08 +0200, Waldemar Brodkorb wrote:
> Hi,
> Thomas Petazzoni wrote,
> 
> > 
> > > 
> > > 3. Regarding purity of standards I may agree that we as more knowledgeable
> > > ? ?engineers need to educate our users and resist temptation to return to
> > > ? ?deprecated things. But as an advocate of my users I'd say that usability
> > > ? ?and support of wider packages might be even more important.
> > 
> > Yes, I agree that there is a balance between "purity" and "pragmatism".
> > 
> > I don't have a very strong opinion on this FTS enabled or not. I don't
> > remember the size measurements with FTS enabled/disabled. Perhaps we
> > should just enable all features needed by Buildroot packages in our
> > uClibc configuration.
> 
> That would be indeed the best policy!
> 
> And I don't think a lot is missing. May be just FTS!

Well there might be more things but still I'd prefer to enable more
packages by default if it doesn't affect entire system (especially with
those "special" packages not enabled) a lot.

I mean as long as we don't introduce significant increase of either
memory footprint of existing system or cause run-time overhead it's
good to allow more packages to be built.

That said if someone wants more stripped down system it's easier
to disable uClibc options (directly via uclibc-menuconfig) compared
to:
?a) Enabling extra options in uClibc plus
?b) Patch Buildroot
to get some extra packages.

-Alexey

      parent reply	other threads:[~2017-10-13 16:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-13 14:25 [Buildroot] [PATCH 1/2] uclibc-ng: enable fts in default config file Adam Duskett
2017-07-13 14:25 ` [Buildroot] [PATCH 2/2] selinux packages: change glibc check to musl check Adam Duskett
2017-07-13 17:32 ` [Buildroot] [PATCH 1/2] uclibc-ng: enable fts in default config file Thomas Petazzoni
2017-07-13 17:41   ` Adam Duskett
2017-07-15  9:44 ` Thomas Petazzoni
2017-07-15 15:15   ` Peter Korsgaard
2017-07-15 17:16     ` Adam Duskett
2017-07-15 19:48     ` Thomas Petazzoni
2017-07-15 20:09       ` Adam Duskett
2017-07-16 15:53       ` Peter Korsgaard
2017-07-16 16:43         ` Waldemar Brodkorb
2017-07-16 17:40           ` Adam Duskett
2017-07-16 18:46             ` Yann E. MORIN
2017-07-18 19:24           ` Arnout Vandecappelle
2017-07-18 21:06             ` Thomas Petazzoni
2017-07-18 21:07               ` Waldemar Brodkorb
2017-10-12  1:06                 ` Alexey Brodkin
2017-10-12  7:52                   ` Thomas Petazzoni
2017-10-12 18:08                     ` Waldemar Brodkorb
2017-10-12 18:56                       ` ratbert90
2017-10-13 16:59                       ` Alexey Brodkin [this message]

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=1507913966.3810.38.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox