From: "Jörg Krause" <jkrause@posteo.de>
To: buildroot@busybox.net
Subject: [Buildroot] libdaemons localstatedir /usr/var
Date: Fri, 17 Oct 2014 02:21:29 +0200 [thread overview]
Message-ID: <54406109.4050202@posteo.de> (raw)
In-Reply-To: <543A7D79.7010008@mind.be>
Dear Thomas Petazzoni,
Dear Arnout Vandecappelle,
On 10/12/2014 03:09 PM, Arnout Vandecappelle wrote:
> On 12/10/14 11:26, J?rg Krause wrote:
>>> >>Isn't --localstatedir a common autoconf variable ? I see 26 packages
>>> >>passing --localstatedir=/var in Buildroot. Maybe it's time to move as a
>>> >>common definition, like --prefix=/usr ?
>> >
>> >Yes, it is. There was a discussion on the mailing list long time ago:
>> >
>> > Making --localstatedir=/var global?
>> > (http://lists.busybox.net/pipermail/buildroot/2011-April/042918.html.)
>> >
>> >And also this one:
>> >
>> > Bizarre things on the allyespackageconfig build
>> > (http://lists.busybox.net/pipermail/buildroot/2013-May/071856.html)
> +1 to making it a global pkg-autotools option. J?rg, care to prepare a patch
> for that? Removing the existing --localstatedir should be a separate patch then.
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.
* 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"`")
* mysql: localstatedir sets the location for database directories and
other files. Not sure how to handle this.
Do you have any suggestions?
J?rg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20141017/1dcc90c1/attachment.html>
next prev parent reply other threads:[~2014-10-17 0:21 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 [this message]
2014-10-17 8:53 ` 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=54406109.4050202@posteo.de \
--to=jkrause@posteo.de \
--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