custom install directory with bdist_wininst
I'd like to give the user control over where the files get installed. It looks like distutils installs into site-packages by default, and there's no way to override it. The UI shows the destination directory in a box that looks like it should be editable, but it isn't. If you run setup.py install, you can pass a --home that affects where files are installed. I'm looking for something similar on Windows. Jeremy
On 30 Jun 2003 15:11:11 -0400, Jeremy Hylton wrote:
I'd like to give the user control over where the files get installed. It looks like distutils installs into site-packages by default, and there's no way to override it. The UI shows the destination directory in a box that looks like it should be editable, but it isn't.
If you run setup.py install, you can pass a --home that affects where files are installed. I'm looking for something similar on Windows.
--install-data should work on Windows (while --home is Unix centric). That is out of the box, and of course you can always overload the command class for more complex things. Ciao, Jürgen -- Jürgen Hermann, Developer WEB.DE AG, http://webde-ag.de/
On Tue, 2003-07-01 at 10:53, Juergen Hermann wrote:
--install-data should work on Windows (while --home is Unix centric). That is out of the box, and of course you can always overload the command class for more complex things.
I'm not sure if I understand. Is this an argument that the user passes to the Windows installer upon execution? I'm not interested in arguments to install, but in allowing user similar control using a binary installer. Jeremy
Jeremy Hylton wrote:
On Tue, 2003-07-01 at 10:53, Juergen Hermann wrote:
--install-data should work on Windows (while --home is Unix centric). That is out of the box, and of course you can always overload the command class for more complex things.
I'm not sure if I understand. Is this an argument that the user passes to the Windows installer upon execution? I'm not interested in arguments to install, but in allowing user similar control using a binary installer.
While the source code for the wininst installer is available, I'm not sure whether it would be easy to add this kind of functionality. You will probably want to use a different installer on Windows for these things, such as InnoSetup -- a bdist_inno would be *really* nice to have, because Inno offers so much more flexibility. -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, Jul 01 2003)
Python/Zope Products & Consulting ... http://www.egenix.com/ mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
2003-07-01: Released mxODBC Zope DA for FreeBSD 1.0.6 beta 1
"M.-A. Lemburg" <mal@lemburg.com> writes:
Jeremy Hylton wrote:
On Tue, 2003-07-01 at 10:53, Juergen Hermann wrote:
--install-data should work on Windows (while --home is Unix centric). That is out of the box, and of course you can always overload the command class for more complex things. I'm not sure if I understand. Is this an argument that the user passes to the Windows installer upon execution? I'm not interested in arguments to install, but in allowing user similar control using a binary installer.
While the source code for the wininst installer is available, I'm not sure whether it would be easy to add this kind of functionality.
Correct.
You will probably want to use a different installer on Windows for these things, such as InnoSetup -- a bdist_inno would be *really* nice to have, because Inno offers so much more flexibility.
This is one possibility, another one is to treat the bdist_wininst created installer as a zipfile, and use a Python script to extract the files and install them. I have no need for either of them, and no time (not motivation) to write them. Thomas
participants (4)
-
Jeremy Hylton -
Juergen Hermann -
M.-A. Lemburg -
Thomas Heller