From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Extend and use the <pkg>_CONFIG_FIXUP infra
Date: Thu, 7 Feb 2013 14:39:34 +0100 [thread overview]
Message-ID: <20130207143934.5a335849@skate> (raw)
In-Reply-To: <1360192218-30930-1-git-send-email-thomas.petazzoni@free-electrons.com>
Peter,
In the following patch series, if we agree on "[PATCH 1/5] package:
rename <pkg>_CONFIG_FIXUP to <pkg>_CONFIG_SCRIPTS", then I believe it
would be better to take it for 2013.02 so that we don't have
<pkg>_CONFIG_FIXUP introduced in 2013.02 and then later a rename of
this new variable.
However, the other patches, 2 to 5, should probably not be taken for
2013.02, but only applied to -next once it opens.
Best regards,
Thomas
On Thu, 7 Feb 2013 00:10:13 +0100, Thomas Petazzoni wrote:
> Hello,
>
> This patch series improves on the <pkg>_CONFIG_FIXUP work done by
> Stefan Fr?berg by:
>
> * Renaming the variable to <pkg>_CONFIG_SCRIPTS. I believe this is
> needed, because we will not only "fixup" those files, but also
> remove them from the target directory. Also, I don't think the
> variable name should indicate what will happen to these files. It
> should just indicate what those files are.
>
> * Extending the <pkg>_CONFIG_SCRIPTS handling to remove the config
> scripts from the TARGET_DIR, unless BR2_HAVE_DEVFILES is set (even
> though it is deprecated, it is still here).
>
> * Use <pkg>_CONFIG_SCRIPTS in a number of packages that were already
> fixing manually their <foo>-config script and for which the new
> infrastructure does exactly the same thing.
>
> * Use <pkg>_CONFIG_SCRIPTS in a number of packages that were doing a
> bit more than the infrastructure: fixing the includedir and libdir
> fields. A manual inspection of each of those packages shows that by
> default, the includedir and libdir are described relatively to
> prefix and exec_prefix, so fixing up those is sufficient, and this
> is what the infrastructure does.
>
> * Use <pkg>_CONFIG_SCRIPTS to fix up gpg-error-config installed by
> the libgpg-error package. This is done separately from the previous
> patch, because libgpg-error was not previously doing any fix up of
> its gpg-error-config script.
>
> Best regards,
>
> Thomas
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-02-07 13:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 23:10 [Buildroot] Extend and use the <pkg>_CONFIG_FIXUP infra Thomas Petazzoni
2013-02-06 23:10 ` [Buildroot] [PATCH 1/5] package: rename <pkg>_CONFIG_FIXUP to <pkg>_CONFIG_SCRIPTS Thomas Petazzoni
2013-02-06 23:59 ` Arnout Vandecappelle
2013-02-07 15:10 ` Samuel Martin
2013-02-06 23:10 ` [Buildroot] [PATCH 2/5] package: remove scripts listed in <pkg>_CONFIG_SCRIPTS from target Thomas Petazzoni
2013-02-07 0:07 ` Arnout Vandecappelle
2013-02-07 15:28 ` Samuel Martin
2013-02-06 23:10 ` [Buildroot] [PATCH 3/5] package: use <pkg>_CONFIG_SCRIPTS wherever possible Thomas Petazzoni
2013-02-07 6:52 ` Arnout Vandecappelle
2013-02-06 23:10 ` [Buildroot] [PATCH 4/5] package: use <pkg>_CONFIG_SCRIPTS in packages that used special handling Thomas Petazzoni
2013-02-07 14:43 ` Samuel Martin
2013-02-06 23:10 ` [Buildroot] [PATCH 5/5] libgpg-error: use <pkg>_CONFIG_SCRIPTS Thomas Petazzoni
2013-02-07 14:44 ` Samuel Martin
2013-02-07 13:39 ` Thomas Petazzoni [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=20130207143934.5a335849@skate \
--to=thomas.petazzoni@free-electrons.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