All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arun Sharma <arun.sharma@intel.com>
To: xen-devel@lists.sourceforge.net
Subject: make dist and python files
Date: Tue, 11 Jan 2005 10:29:07 -0800	[thread overview]
Message-ID: <41E41AF3.9010400@intel.com> (raw)


In the xeno-unstable tree,

# make install

populates python files in /usr/lib/python2.3/site-packages/xen

However,

# make dist

populates them in

dist/install/lib/python

For people trying to package up Xen into an installable object (rpm/deb 
whatever) this creates a problem.

So my question is, why not have

# make dist

also populate

dist/install/usr/lib/python2.3/site-packages/xen

Of course, this won't work for situations where the build machine and 
the target machine have a different version of python.

Relevant snippet from tools/python/Makefile:

install: all
         if [ "$(prefix)" = "" ]; then                   \
             python setup.py install;                    \
         elif [ "$(dist)" = "yes" ]; then                \
             python setup.py install --home="$(prefix)"; \
         else                                            \
             python setup.py install --root="$(prefix)"; \
         fi

	-Arun



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

             reply	other threads:[~2005-01-11 18:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-11 18:29 Arun Sharma [this message]
2005-01-11 19:31 ` make dist and python files Keir Fraser
2005-01-11 22:28   ` Arun Sharma
2005-01-11 22:43     ` Keir Fraser
2005-01-12  2:46 ` Adam Heath

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=41E41AF3.9010400@intel.com \
    --to=arun.sharma@intel.com \
    --cc=xen-devel@lists.sourceforge.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 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.