From: George Dunlap <george.dunlap@eu.citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
Xen Devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] Fix pygrub install.
Date: Fri, 1 Jun 2012 11:11:34 +0100 [thread overview]
Message-ID: <4FC89556.7090502@eu.citrix.com> (raw)
In-Reply-To: <1338539390.17466.26.camel@zakaz.uk.xensource.com>
On 01/06/12 09:29, Ian Campbell wrote:
> On Thu, 2012-05-31 at 10:54 +0100, Anthony PERARD wrote:
>> On Thu, May 31, 2012 at 10:42 AM, George Dunlap
>> <George.Dunlap@eu.citrix.com> wrote:
>>> The strange thing is that there *is* a pygrub in the right place, so
>>> it appears that thefollowing line ($INSTALL_PYTHON_PROG) is redundant?
>> It's seems that the right on the script are already set to 755 by the
>> setup.py, so this $INSTALL_PYTHON_PROG line is probably an extra.
> What is the conclusion here? Is the original patch correct and/or is
> there a subsequent additional fix?
There is a bug (pygrub is installed both in $(DESTDIR)/foo and
$(DESTDIR)/$(DESTDIR)/foo), and Anthony's first patch (AFAICT) correctly
fixes the bug (only installed in $(DESTDIR).
I think there is a redundant command in the Makefile as well, where
pygrub will be copied to $(DESTDIR)/foo twice. That doesn't cause
incorrect behavior, but I would probably still consider it a bug.
So the original patch is correct, but there is a subsequent fix.
> My scripts does things like:
> make -C tools XEN_TARGET_ARCH=x86_32 DESTDIR=/tmp/tmp0_hnbt LIBXL_TESTIDL_SEED=42 debug=y -j12 install
> then tars up /tmp/tmp0_hnbt, copies it to my test box and untars. I've
> just noticed on my test box:
> # ls -dl /tmp/tmp*
> drwxr-xr-x 3 root root 4096 Jun 1 09:26 /tmp/tmp0_hnbt
> drwxr-xr-x 3 root root 4096 May 18 11:11 /tmp/tmp8D2Mvc
> drwxr-xr-x 3 root root 4096 May 25 10:21 /tmp/tmpAd2OFq
> drwxr-xr-x 3 root root 4096 May 18 15:05 /tmp/tmpEqYZpf
> [...]
> # find /tmp/tmp* -name pygrub | wc -l
> 19
The "right thing" is to find find 2 files named "pygrub" per directory
(a binary at /usr/lib/xen/bin/pygrub and a link to that binary at
/usr/bin/pygrub, for compatibility). Without Anthony's patch you would
get 3. Not sure how that corresponds to the directories you have there...
-George
next prev parent reply other threads:[~2012-06-01 10:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 16:56 [PATCH] Fix pygrub install Anthony PERARD
2012-05-31 9:17 ` George Dunlap
2012-05-31 9:42 ` George Dunlap
2012-05-31 9:54 ` Anthony PERARD
2012-06-01 8:29 ` Ian Campbell
2012-06-01 10:11 ` George Dunlap [this message]
2012-06-01 10:19 ` Ian Campbell
2012-06-01 10:21 ` Roger Pau Monne
2012-06-01 10:30 ` Ian Campbell
2012-06-01 10:35 ` Roger Pau Monne
2012-06-01 10:35 ` George Dunlap
2012-06-01 11:14 ` Anthony PERARD
2012-06-08 14:56 ` George Dunlap
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=4FC89556.7090502@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=anthony.perard@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.