WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] debian python-install.patch (3 of 5)

On Sun, 2005-02-06 at 18:00 +0000, Ian Pratt wrote:
>  > > >  --home causes python's distutils to install into
> > > > /usr/lib/python/, while
> > > >  --root causes it to install into
> > > > /usr/lib/python$ver/site-packages, which
> > > >  is the more correct location.
> > Er, in all packages I have ever used, make dist has given me 
> > a tree(which is
> > normally placed into a tar by upstream, and 'dist'ributed, 
> > hence the name),
> > that can then be optionally overlayed ontop an already 
> > installed system.
> 
> Yes, but its quite usual for bpeople to install Xen on a different
> system to which is was built (e.g. our binary install tar file).
> Installing into /usr/lib/python/ means that it'll be found on the module
> search path, whereas /usr/lib/python$ver/site-packages will only work if
> the version is the same.

Mind please that I have no empirical proof, just personal experience and
opinions/preferences expressed to me by admins I know.

I would have to disagree here. If Xen is to be taken seriously in a
commercial environment, then it's going to have to be available as a
dist binary from either redhat, suse, debina, or another top level linux
distro IMHO. 

Having to compile things for every machine tends to turn potential users
off that aren't programmers or gentoo/*bsd afficianados from my
experience.

Heck, this is why I stated packaging 1.3 in the first place. I just
couldn't deal with deploying by hand every couple of days. I really
needed it to be automatic as possible.

> 
> Do you use the dist directory for your package build? If not, why do you
> care?
>  
> If you do, maybe we'll need some flag to change the behaviour. This will
> all be rather more obvious if we can get the debian package build runes
> checked into the xen repo.
> 
> Thanks,
> Ian 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/xen-devel



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel