Hello again, I''ve just noticed that a recent change breaks my RPM package installation. The diff extract is: --- 1.10/tools/xc/py/Makefile Thu Mar 18 04:21:30 2004+++ 1.11/tools/xc/py/Makefile Thu Mar 18 04:21:30 2004@@ -4,15 +4,7 @@ install: all if [ "$(prefix)" = "" ]; then python setup.py install; \ - else python setup.py install --root "$(prefix)"; fi + else python setup.py install --home="$(prefix)"; fi This seems to move files that were in /usr/lib/python-2.2/site-packages to /lib/python, with the effect that tools such as xc_dom_control.py fail with "ImportError: No module named Xc". It appears there are similar problems with the make files for xend and xentrace too. Am I the only one suffering from this change? Cheers, Sean. -- Sean Atkinson <sean@netproject.com> Netproject ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> Hello again, > > I''ve just noticed that a recent change breaks my RPM package > installation. The diff extract is: > --- 1.10/tools/xc/py/Makefile Thu Mar 18 04:21:30 2004+++ > 1.11/tools/xc/py/Makefile Thu Mar 18 04:21:30 2004@@ -4,15 +4,7 @@ > > install: all > if [ "$(prefix)" = "" ]; then python setup.py install; \ > - else python setup.py install --root "$(prefix)"; fi > + else python setup.py install --home="$(prefix)"; fiLooking at the web interface, it appears the change was contributed by Adam Heath, as part of his helpful effort to make Xen/Xenolinux Debian complient: http://xen.bkbits.net:8080/xeno-1.2.bk/diffs/tools/xc/py/Makefile@1.9?nav=index.html|src/.|src/tools|src/tools/xc|src/tools/xc/py|hist/tools/xc/py/Makefile Can you guys duke it out to figure out what the correct runes should be, and we''ll apply the patch. Makefiles and installation scripts are not our strong point... Thanks, Ian> This seems to move files that were in /usr/lib/python-2.2/site-packages > to /lib/python, with the effect that tools such as xc_dom_control.py > fail with "ImportError: No module named Xc". It appears there are > similar problems with the make files for xend and xentrace too. > > Am I the only one suffering from this change? > > Cheers, > > Sean. > > -- > Sean Atkinson <sean@netproject.com> > Netproject > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Hi,> Looking at the web interface, it appears the change was > contributed by Adam Heath, as part of his helpful effort to make > Xen/Xenolinux Debian complient: > > http://xen.bkbits.net:8080/xeno-1.2.bk/diffs/tools/xc/py/Makefile@1.9?nav=index.html|src/.|src/tools|src/tools/xc|src/tools/xc/py|hist/tools/xc/py/Makefile > > Can you guys duke it out to figure out what the correct runes > should be, and we''ll apply the patch. Makefiles and installation > scripts are not our strong point...I''ve just hunted out some relevant documentation: http://www.python.org/doc/current/inst/alt-install-windows.html This suggests we should revert to the earlier "root" behaviour for a distribution installation rather than a local "home" installation. I also notice that my Debian testing "sarge" install uses /usr/lib/python2.{1,3}, so hopefully the Debian package should work there too? Attached is my patch to revert behaviour. I''ve built my RPM with it and checked that the tools work again. If everyone''s happy should we apply it? Cheers, Sean. -- Sean Atkinson <sean@netproject.com> Netproject