On Wed, Jun 14, 2006 at 06:45:12AM -0500, Anthony Liguori wrote:
> Ewan Mellor wrote:
> >On Thu, Jun 08, 2006 at 08:09:06PM -0500, Anthony Liguori wrote:
> >
> >
> >>This seems exceptionally evil and is definitely a PITA. What was the
> >>original problem that led us to do this? I'd like to take a stab at
> >>correcting it so we can have a more sane installation.
> >>
> >
> >If you're going to fix this, then great. Perhaps you could make it:
> >
>
> I would love to, if patches are willing to be taken.
Certainly we'll take the patch.
> >a) use the proper Python distutils if installed;
> >
>
> I think we already are aren't we? I thought the crux of the problem was
> that people are relying on having a deterministic install path so that
> it can be deployed on many machines (regardless of Python version). We
> would have to break this "feature". I'm happy to do that of course :-)
I meant use distutils in the install script, i.e. on the destination machine.
What people want to be able to do is create a dist directory, copy it
wholesale over to a target host, and then run install.sh and have the right
thing happen. If the install.sh was clever enough to drop things into the
correct Python directory, then that's great and doesn't break anything.
In the case where people use "make install" directly, yes, distutils is used
already.
Some people copy the dist directory straight onto the root directory on their
test box (many of the developers here, for example). That's not really
supported, because you end up with both the hotplug and udev scripts
installed, for example, but it is handy for developers, so it would be good to
preserve that behaviour. In other words, you still need a
dist/usr/lib/python/ directory to be created, even if install.sh doesn't copy
those files directly to that directory when it runs.
Thanks,
Ewan.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home