Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] system/skeleton: make nsswitch install conditional
Date: Mon, 20 Oct 2014 10:34:09 -0300	[thread overview]
Message-ID: <54450F51.5050801@zacarias.com.ar> (raw)
In-Reply-To: <20141020152759.4f438890@free-electrons.com>

On 10/20/2014 10:27 AM, Thomas Petazzoni wrote:

> Well, it's just that I still have my pet project of graphing the size
> installed by each package. And for this, every file not installed by a
> package is a bit annoying, as we don't know to which package we should
> account the installation of the file.

You've got bigger fish to care about before this tiny file, like
COPY_GCONV_LIBS in toolchain/toolchain.mk, or:

gustavoz at asgard ~/git/buildroot/package $ find . -name \*.mk -exec grep
--with-filename TARGET_FINALIZE {} \;
./perl/perl.mk:TARGET_FINALIZE_HOOKS += PERL_FINALIZE_TARGET
./luarocks/luarocks.mk:TARGET_FINALIZE_HOOKS += LUAROCKS_FINALIZE_TARGET
./google-breakpad/google-breakpad.mk:TARGET_FINALIZE_HOOKS +=
GOOGLE_BREAKPAD_EXTRACT_SYMBOLS
./python/python.mk:TARGET_FINALIZE_HOOKS += PYTHON_FINALIZE_TARGET
./python3/python3.mk:TARGET_FINALIZE_HOOKS += PYTHON3_FINALIZE_TARGET

Besides it's a file that in essence belongs to skeleton, just
conditional on (e)glibc.
You'll have to deal with the other skeleton files as well IMHO, just
treat is as such.
(negative logic could be used, remove if it's not needed, but i don't
think it'll change anything WRT your pet project).
Regards.

  reply	other threads:[~2014-10-20 13:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-20 12:28 [Buildroot] [PATCH 1/2] system/skeleton: make nsswitch install conditional Gustavo Zacarias
2014-10-20 12:28 ` [Buildroot] [PATCH 2/2] glibc/nsswitch.conf: also lookup on dns for networks Gustavo Zacarias
2014-10-20 13:02 ` [Buildroot] [PATCH 1/2] system/skeleton: make nsswitch install conditional Thomas Petazzoni
2014-10-20 13:19   ` Gustavo Zacarias
2014-10-20 13:27     ` Thomas Petazzoni
2014-10-20 13:34       ` Gustavo Zacarias [this message]
2014-10-20 13:37         ` Thomas Petazzoni
2014-10-20 13:43           ` Gustavo Zacarias
2014-10-20 13:54             ` Thomas Petazzoni
2014-10-20 14:12               ` Gustavo Zacarias
2014-10-20 14:28                 ` Thomas Petazzoni
2014-10-22 14:10                   ` Maxime Hadjinlian
2014-10-22 19:44                     ` Gustavo Zacarias
2014-10-22 19:49                       ` Gustavo Zacarias
2014-10-23 17:47                         ` Maxime Hadjinlian
2014-10-21 18:49   ` Arnout Vandecappelle
2014-10-25 10:49 ` Thomas Petazzoni

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=54450F51.5050801@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox