From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] exim: get rid of the convert the custom config file boolean knob
Date: Wed, 16 Jul 2014 19:37:26 +0200 [thread overview]
Message-ID: <20140716193726.406e233d@free-electrons.com> (raw)
In-Reply-To: <20140716172836.GC9252@free.fr>
Dear Yann E. MORIN,
On Wed, 16 Jul 2014 19:28:36 +0200, Yann E. MORIN wrote:
> > + reasonable settings. If you want to override the configuration file
> > + generated by Buildroot with a customized file, set here the path
> > + to your configuration file in BR2_PACKAGE_EXIM_CUSTOM_CONFIG_FILE.
>
> But what if the user has .include directives in his config file?
> Can't we just accept more than one file here, and accept wildcards,
> maybe?
I believe you're confusing two things here:
* The exim runtime configuration file, which can have .include
directives and so on.
* The exim compile-time configuration file, which is what this patch
is about. It just contains a series of "variable = value" pairs, and
is completely distinct from the exim runtime configuration file.
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 17:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 16:11 [Buildroot] [PATCH] exim: get rid of the convert the custom config file boolean knob Luca Ceresoli
2014-07-16 17:28 ` Yann E. MORIN
2014-07-16 17:37 ` Thomas Petazzoni [this message]
2014-07-16 19:49 ` Yann E. MORIN
2014-07-16 17:48 ` 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=20140716193726.406e233d@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.