I think I have it figured out. Fink requires installing a package in a temporary root install that is then turned into a deb. This makes the pth files have bad paths. If I manage the paths in the pth files after the install, then things seem to work. It looks like i will have to manage the easy_install.pth anyway since if it ends up in a deb, then other packages can't work with it. I'm going to create PostInstall, PostRm commands to take care of that.
<br><br>/sw/bin/easy_install -h is now running so I think I am on the right track.<br><br>-kurt<br><br><div><span class="gmail_quote">On 3/29/06, <b class="gmail_sendername">Phillip J. Eby</b> <<a href="mailto:pje@telecommunity.com">
pje@telecommunity.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">At 06:42 PM 3/29/2006 -0500, Kurt Schwehr wrote:<br>
>Phillip and others,<br>><br>>Does this look like it is installed correctly? Or is it that I am calling<br>>setup.py when I should be calling ez_setup? And what should I pass to<br>>ez_setup? It does look like setuptools are installed incorrectly since
<br>>easy_install -h does not run. So what is the right way?<br><br>If you are packaging setuptools for use with a system packager, you should use:<br><br> python setup.py install --root=/some/pseudoroot<br><br>If you are using setuptools
0.6a10 or earlier, you *also* need<br>--single-version-externally-managed for this to work. 0.6a11 (which I just<br>released a few minutes ago) automatically sets<br>--single-version-externally-managed if you specify a --root, so you might
<br>want to just go ahead and upgrade, especially since 0.6a11 has a lot of<br>other changes to improve compatibility with system packagers.<br><br>For example, while 0.6a10 will complain about system-installed versions of
<br>a package as conflicting with a package that is being installed, 0.6a11<br>installs things such that there are no conflicts. 0.6a11 also supports<br>making system packages for projects containing namespace packages, without
<br>causing inter-package conflicts for the packaging system.<br><br></blockquote></div><br>