From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arun Sharma Subject: make dist and python files Date: Tue, 11 Jan 2005 10:29:07 -0800 Message-ID: <41E41AF3.9010400@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: xen-devel@lists.sourceforge.net List-Id: xen-devel@lists.xenproject.org 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