Re: [PyX-devel] Installing PyX to a non-standard location.

[Andrea R. <ari...@pi...>]

On 18 Nov 2004, at 08:50, Andre Wobst wrote:

> Oh my goodness.
>
> What I don't understand upto now is, why the pyxrc gets installed to
> "/etc". In step 4 above everything is fine. With the siteconfig below
> it should work on this installation position. Couldn't you do this by
> using the distutils install command with the proper --root and
> --prefix and without any patch? Then everything is fine, and you could
> copy it to the final location ... only the siteconfig.py would be
> needed to be adjusted (since you copy it around).

I'vee tried your suggestion using both --root and --prefix but it 
doesn't work. The problem here is that dpkg installs files following 
the tree rooted to the directory given through --root option, not to 
the directory given through --prefix option. May be an example makes 
this clear: if --root is /foo/bar then dpkg will discharge this prefix 
from the installation path, so that a file that is under 
/foo/bar/foofoo/barbar will be installed in /foofoo/barbar.

Since --root is '/sw/src/root-pyx-wierda-py23-0.7-6', pyxrc will be 
written in /etc instead that in /sw/etc. As far as I can understand if 
you want to make your setup script to works without patch with fink you 
must take your paths relative to --prefix and not to --root. But I 
don't know if this could work well on other platforms. Anyway I think 
it would be better (and even simpler for you) to keep the setup.py 
script as general as possible (I mean not too much targeted to a 
specific platform) and let those who have special needs to patch it. My 
2 cents though...

>> Evetually the @PYTHON_FLAVOR@ is mandatory because Fink still has
>> Python 2.2 and 2.3 flavours and a user may want to have both 
>> installed.
>
> I see. You want to get the shared data installed twice although it
> does not depend on the Python version (and the plattform). But thats
> not what shared data are for. While, ok, you can do it that way,
> another idea would be to make a python-pyx-common package for the
> share data (and a python-pyx-doc for the documentation) and some
> python2.x-pyx packages for the Python scripts. Ok, its a bit overkill,
> but the debian packages do it that way.

You are right, I could create two splitoff for the package one for the 
docs and one for the shared datas. I'll try if it is feasible this 
week-end.

Andrea.