From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3] Make exim more configurable
Date: Wed, 16 Jul 2014 11:03:04 +0200 [thread overview]
Message-ID: <20140716110304.749a1a2f@free-electrons.com> (raw)
In-Reply-To: <53C63CD6.6020104@lucaceresoli.net>
Dear Luca Ceresoli,
On Wed, 16 Jul 2014 10:50:30 +0200, Luca Ceresoli wrote:
> How do the autobuilders handle the same situation for the Linux or
> Barebox custom configuration files? E.g.:
>
> # BR2_LINUX_KERNEL_USE_DEFCONFIG is not set
> BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
> BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE=""
>
> This would fail in the same way. Obvious enough, since for exim I just
> copied the same checks...
>
> Do the autobuilders have a special handling for the kernel and
> bootloaders? If that's the case, of course it would not be viable to do
> it for each and every package.
Since the Linux kernel and bootloader options do not start with
BR2_PACKAGE_* they are not part of the randpackageconfig randomization,
and therefore the autobuilders never build the Linux kernel or the
bootloaders.
We however have a similar situation with other packages, in which case
the autobuilder script comes to help, see for example
http://git.buildroot.net/buildroot-test/tree/scripts/autobuild-run#n244.
> > Options:
> >
> > 1/ Have a default value for BR2_PACKAGE_EXIM_CUSTOM_CONFIG_FILE that
> > actually works.
>
> That would be quite simple. Enough to run a build with
> BR2_PACKAGE_EXIM_CUSTOM_CONFIG disabled, pick the config file from
> the build dir, remove the toolchain additions and put the file in
> packace/exim/default-config.
That is one solution.
> I agree options 2 and 3 would be more annoying.
They are possible, we do this for other packages already.
> Another option is:
>
> 4/ Remove BR2_PACKAGE_EXIM_CUSTOM_CONFIG knob and make exim use the
> custom configuration only if
> BR2_PACKAGE_EXIM_CUSTOM_CONFIG_FILE != "". I assume the
> autobuilders never set BR2_PACKAGE_EXIM_CUSTOM_CONFIG_FILE, do
> they?
Indeed, randpackageconfig only takes care of boolean or tristate
options, so BR2_PACKAGE_EXIM_CUSTOM_CONFIG_FILE would remain empty in
terms of autobuilder testing.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-07-16 9:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 15:56 [Buildroot] [PATCH 0/3] Make exim more configurable Luca Ceresoli
2014-07-04 15:56 ` [Buildroot] [PATCH 1/3] exim: allow using a custom configuration file Luca Ceresoli
2014-07-04 15:56 ` [Buildroot] [PATCH 2/3] exim: make EXIM_USER configurable Luca Ceresoli
2014-07-04 15:56 ` [Buildroot] [PATCH 3/3] exim: generate the user with automatic uid Luca Ceresoli
2014-07-15 19:31 ` [Buildroot] [PATCH 0/3] Make exim more configurable Thomas Petazzoni
2014-07-16 8:18 ` Luca Ceresoli
2014-07-16 8:29 ` Thomas Petazzoni
2014-07-16 9:03 ` Luca Ceresoli
2014-07-16 17:14 ` Yann E. MORIN
2014-07-16 8:24 ` Thomas Petazzoni
2014-07-16 8:50 ` Luca Ceresoli
2014-07-16 9:03 ` Thomas Petazzoni [this message]
2014-07-16 16:15 ` Luca Ceresoli
2014-07-16 22:47 ` Arnout Vandecappelle
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=20140716110304.749a1a2f@free-electrons.com \
--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