From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] libdaemons localstatedir /usr/var
Date: Fri, 17 Oct 2014 10:53:02 +0200 [thread overview]
Message-ID: <20141017105302.6f1f768c@free-electrons.com> (raw)
In-Reply-To: <54406109.4050202@posteo.de>
Dear J?rg Krause,
On Fri, 17 Oct 2014 02:21:29 +0200, J?rg Krause wrote:
> I started with setting --localstatedir=/var globally. There are three
> packages which set localstatedir to another directory as /var:
>
> * dhcp: It's save to remove local localstatedir here. Is it used for
> setting leases and pid files. All leases and pid files are set as config
> options in the dhcp.mk.
Ok.
> * proftpd: Uses localstatedir to set the location of the pid file:
>
> AC_DEFINE_UNQUOTED(PR_RUN_DIR, "`eval echo "${localstatedir}"`")
> AC_DEFINE_UNQUOTED(PR_PID_FILE_PATH, "`eval echo
> "${localstatedir}/proftpd.pid"`")
>
> Maybe a patch should set it to?:
>
> AC_DEFINE_UNQUOTED(PR_RUN_DIR, "`eval echo "${localstatedir}/run"`")
> AC_DEFINE_UNQUOTED(PR_PID_FILE_PATH, "`eval echo
> "${localstatedir}/run/proftpd.pid"`")
Sounds good.
> * mysql: localstatedir sets the location for database directories and
> other files. Not sure how to handle this.
You can keep a custom --localstatedir in mysql.mk.
One of the good thing with autoconf is that if you pass:
--localstatedir=/var ... --localstatedir=/var/something
Then /var/something will be used. So, we can set --localstatedir=/var
by default in the infrastructure, and still have certain packages doing
weird things override it.
So this also means that your patch should be in at least two steps: one
step adding --localstatedir=/var to the infrastructure, and then one
patch removing --localstatedir=/var from the packages where this is no
longer needed.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-10-17 8:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-12 0:55 [Buildroot] libdaemons localstatedir /usr/var Jörg Krause
2014-10-12 7:18 ` Thomas Petazzoni
2014-10-12 9:26 ` Jörg Krause
2014-10-12 13:09 ` Arnout Vandecappelle
2014-10-12 15:56 ` Jörg Krause
2014-10-12 16:13 ` Thomas Petazzoni
2014-10-12 16:18 ` Arnout Vandecappelle
2014-10-17 0:21 ` Jörg Krause
2014-10-17 8:53 ` 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=20141017105302.6f1f768c@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