All of lore.kernel.org
 help / color / mirror / Atom feed
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: prefix and python site-packages
Date: Wed, 23 Apr 2014 12:05:51 +0200	[thread overview]
Message-ID: <20140423100550.GA5825@aepfle.de> (raw)
In-Reply-To: <1398246891.18537.4.camel@kazak.uk.xensource.com>

On Wed, Apr 23, Ian Campbell wrote:

> On Wed, 2014-04-23 at 11:33 +0200, Olaf Hering wrote:
> > On Wed, Apr 23, Ian Campbell wrote:
> > 
> > > I don't suppose python has an analogue of -rpath?
> > 
> > Looks like sys.path.insert() is the python way of rpath. 
> > Would it be acceptable to tweak pygrub at install time and insert
> > something like the hack I had posted earlier?
> 
> Does Python distutils (used by tools/pygrub/setup.py) not have any
> support for doing this sort of thing automatically?

I have to check.
But how would pygrub, or any other helloworld.py, know that it was
installed into --prefix= and its libs/modules are also in --prefix=? I
think something has to be hardcoded, unless PYTHONPATH or simimar is
used to point to a specific --prefix=.

> >  From what I have seen
> > pygrub is the only remaining binary using the xen.lowlevel stuff.
> 
> It only uses it to decide if the hypervisor supports 64 bit PV guests.
> Since the we no longer have a 32-bit hypervisor perhaps we can just nuke
> that check and sidestep the whole problem?

It also uses fsimage and grub.*, which is also installed below --prefix=

Olaf

  reply	other threads:[~2014-04-23 10:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-23  8:21 prefix and python site-packages Olaf Hering
2014-04-23  9:06 ` Ian Campbell
2014-04-23  9:33   ` Olaf Hering
2014-04-23  9:54     ` Ian Campbell
2014-04-23 10:05       ` Olaf Hering [this message]
2014-04-23 10:08         ` Ian Campbell
2014-04-24 10:55 ` Ian Jackson

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=20140423100550.GA5825@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 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.