Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3] Make exim more configurable
Date: Wed, 16 Jul 2014 10:50:30 +0200	[thread overview]
Message-ID: <53C63CD6.6020104@lucaceresoli.net> (raw)
In-Reply-To: <20140716102439.2bcff4ce@free-electrons.com>

Dear Thomas,

Thomas Petazzoni wrote:
> Luca,
>
> On Tue, 15 Jul 2014 21:31:25 +0200, Thomas Petazzoni wrote:
>
>>> Luca Ceresoli (3):
>>>    exim: allow using a custom configuration file
>>
>> Thanks, I've applied this patch.
>
> This patch is causing build issues:
> http://autobuild.buildroot.org/results/0db/0db54c555f6c7e635ebf99f86b3f91dc31e441f0/build-end.log.
> This happens when randpackageconfig decides to:
>
>    BR2_PACKAGE_EXIM_CUSTOM_CONFIG=y
>
> But of course:
>
>    BR2_PACKAGE_EXIM_CUSTOM_CONFIG_FILE=""

Argh! :(

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.

>
> 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.

I can do that, or we can go for option 4 below.

>
>   2/ Let me know a proper value for BR2_PACKAGE_EXIM_CUSTOM_CONFIG_FILE
>      that the autobuilder scripts would inject into the configuration
>      when BR2_PACKAGE_EXIM_CUSTOM_CONFIG=y. This requires changing the
>      autobuilder scripts, and I've no control over the autobuilder
>      executed by Peter.
>
>   3/ Exclude configuration that have BR2_PACKAGE_EXIM_CUSTOM_CONFIG=y in
>      the autobuilder script. This also requires changing the autobuilder
>      scripts, with the same drawback as above: there's nothing I can do
>      for Peter's autobuilder machines.

I agree options 2 and 3 would be more annoying.

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?

-- 
Luca

  reply	other threads:[~2014-07-16  8:50 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 [this message]
2014-07-16  9:03       ` Thomas Petazzoni
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=53C63CD6.6020104@lucaceresoli.net \
    --to=luca@lucaceresoli.net \
    --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