From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: Wei Liu <wei.liu2@citrix.com>,
xen-devel@lists.xen.org, Ian Jackson <ian.jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH for-xen-4.5] tools/hotplug: use configure --sysconfdir result
Date: Wed, 12 Nov 2014 13:56:00 -0500 [thread overview]
Message-ID: <20141112185600.GB4898@laptop.dumpdata.com> (raw)
In-Reply-To: <20141112172346.GC17230@aepfle.de>
On Wed, Nov 12, 2014 at 06:23:46PM +0100, Olaf Hering wrote:
> On Wed, Nov 12, Konrad Rzeszutek Wilk wrote:
>
> > On Wed, Nov 12, 2014 at 06:06:57PM +0100, Olaf Hering wrote:
> > > On Wed, Nov 12, Konrad Rzeszutek Wilk wrote:
> > >
> > >
> > > > What happens if we do not take that in now but delay to Xen 4.6?
> > >
> > > I will be very unhappy...
> > > I mean, what exactly is the concern here?!
> >
> > I need to know what the risk is if this does not go in. We
> > are at RC2 and I really want to make the amount of patches
> > that go in be a trickle.
>
> Its risk free.
>
> > > > Will systemd still correctly work? It looks like it will and
> > > > this is just an improvement that makes the code be more streamlined.
> > > >
> > > > It does not fix a bug (at least that is what I see from
> > > > reading), I believe this should be deferred to Xen 4.6.
> > >
> > > It does fix a bug. If the whole thing was configured with --prefix=X
> > > --sysconfdir=Y parts of it will still refer to hardcoded paths entirely
> > > unrelated to what was just installed with 'make install'.
> >
> > How often does that happen? Do the two paths that are specified
> > in the code cover 99% of the use-cases?
>
> It covers 100% of the use cases. Just today someone complained on
> xen-users that stuff isnt appearing below /usr/local (not sure why, not
> our fault), but even if it was there it wouldnt be used because the code
> hardcodes /etc.
Excellent.
Release-Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>
> Olaf
next prev parent reply other threads:[~2014-11-12 18:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 6:55 [PATCH for-xen-4.5] tools/hotplug: use configure --sysconfdir result Olaf Hering
2014-10-14 9:31 ` Ian Campbell
2014-10-14 9:35 ` Olaf Hering
2014-10-14 14:02 ` Ian Jackson
2014-10-14 14:18 ` Olaf Hering
2014-11-12 11:06 ` Olaf Hering
2014-11-12 11:12 ` Ian Campbell
2014-11-12 15:21 ` Konrad Rzeszutek Wilk
2014-11-12 17:06 ` Olaf Hering
2014-11-12 17:16 ` Konrad Rzeszutek Wilk
2014-11-12 17:23 ` Olaf Hering
2014-11-12 18:56 ` Konrad Rzeszutek Wilk [this message]
2014-11-14 10:35 ` Ian Campbell
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=20141112185600.GB4898@laptop.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=olaf@aepfle.de \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@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 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.