From: Olaf Hering <olaf@aepfle.de>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Ian.Jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: usage of fixed path in hotplug scripts
Date: Tue, 22 Apr 2014 13:37:05 +0200 [thread overview]
Message-ID: <20140422113704.GA16659@aepfle.de> (raw)
In-Reply-To: <1398155617.31707.6.camel@kazak.uk.xensource.com>
On Tue, Apr 22, Ian Campbell wrote:
> I think it would be fine to fix this up, so long as the defaults don't
> change (iirc autoconf has weird ideas about /var aka $localstatedir, see
> 9f7b256146dc "tools: revert to using /var and /etc/")
There can be only one xen.rpm (from make rpmball) active at a time. So I
think its perfectly fine to have a fixed /var dir, without $PREFIX.
For /etc is more complex because some parts are system configuration
(udev), other parts are internal to xen (scripts), and runlevel scripts
can be started manually if needed. Adding $PREFIX to /etc feels wrong.
In any case, I will preserve existing defaults.
Olaf
prev parent reply other threads:[~2014-04-22 11:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 14:06 usage of fixed path in hotplug scripts Olaf Hering
2014-04-22 8:33 ` Ian Campbell
2014-04-22 11:37 ` Olaf Hering [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=20140422113704.GA16659@aepfle.de \
--to=olaf@aepfle.de \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/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;
as well as URLs for NNTP newsgroup(s).