| 2008-04-19 07:46:01 |
Jakob |
bug |
|
|
added bug |
| 2008-04-21 07:49:11 |
Martin Pool |
bzr: status |
New |
Incomplete |
|
| 2008-09-05 12:45:03 |
Jakob |
bzr: status |
Incomplete |
New |
|
| 2008-09-05 12:45:03 |
Jakob |
bzr: statusexplanation |
|
I can't tell what other information I could possibly give, so as far as I can tell it is not an incomplete bug anymore... |
|
| 2008-09-05 17:29:13 |
John A Meinel |
bzr: status |
New |
Incomplete |
|
| 2008-09-05 17:29:13 |
John A Meinel |
bzr: importance |
Undecided |
Low |
|
| 2008-09-05 17:29:13 |
John A Meinel |
bzr: statusexplanation |
I can't tell what other information I could possibly give, so as far as I can tell it is not an incomplete bug anymore... |
What happens if you use:
python setup.py install --prefix=XXXX
rather than
install --home=XXXX
?
On this machine it changes the install layout. I'm not sure if that is sufficient for what you need.
As near as I can tell, neither 'python setup.py install --prefix' or '--home' will set up any custom paths for you (which is unfortunate.) I believe this is just a bug in Python itself. That it cannot install to a custom location *and* configure the search path so that scripts will have the libraries in their default search path.
The only way *I* see around this is to not use python's disutils or setuptools, but to have a completely separate installation mechanism. Which I don't think we'll do.
Does any other program that uses disutils work automatically when installed into a custom location? If so, I'd be happy to inspect their setup.py to figure out how to do the same. |
|
| 2008-09-08 07:13:58 |
Jakob |
bzr: status |
Incomplete |
Fix Released |
|
| 2008-09-08 07:13:58 |
Jakob |
bzr: statusexplanation |
What happens if you use:
python setup.py install --prefix=XXXX
rather than
install --home=XXXX
?
On this machine it changes the install layout. I'm not sure if that is sufficient for what you need.
As near as I can tell, neither 'python setup.py install --prefix' or '--home' will set up any custom paths for you (which is unfortunate.) I believe this is just a bug in Python itself. That it cannot install to a custom location *and* configure the search path so that scripts will have the libraries in their default search path.
The only way *I* see around this is to not use python's disutils or setuptools, but to have a completely separate installation mechanism. Which I don't think we'll do.
Does any other program that uses disutils work automatically when installed into a custom location? If so, I'd be happy to inspect their setup.py to figure out how to do the same. |
Actually, using the --prefix option instead of the --home option solves the issue. From the help of setuptools I got this:
Options for 'install' command:
--prefix installation prefix
--home (Unix only) home directory to install under
So apparently indeed there is a subtle difference, even though I don't see what it is. But that's something for the setuptools-people to answer. My personal feeling though is that the installation instructions in the 'INSTALL' file that comes with bzr, should be changed and it should say to use --prefix instead of --home? |
|
| 2008-09-08 21:41:34 |
Dan Watkins |
bzr: status |
Fix Released |
Invalid |
|
| 2008-09-08 21:41:34 |
Dan Watkins |
bzr: statusexplanation |
Actually, using the --prefix option instead of the --home option solves the issue. From the help of setuptools I got this:
Options for 'install' command:
--prefix installation prefix
--home (Unix only) home directory to install under
So apparently indeed there is a subtle difference, even though I don't see what it is. But that's something for the setuptools-people to answer. My personal feeling though is that the installation instructions in the 'INSTALL' file that comes with bzr, should be changed and it should say to use --prefix instead of --home? |
I think that if we're telling people how to install in their home directory, then using the well-known 'install in home directory' option for the standard Python build system is probably wise.
But this isn't really relevant to this bug. If you feel strongly about it, please feel free to open another bug. :) |
|
