➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Get rid of make frameworkinstall
Type: Stage:
Components: macOS Versions:
process
Status: closed Resolution: rejected
Dependencies: Superseder:
Assigned To: jackjansen Nosy List: jackjansen
Priority: normal Keywords:

Created on 2002-01-18 16:01 by jackjansen, last changed 2022-04-10 16:04 by admin. This issue is now closed.

Messages (2)
msg8843 - (view) Author: Jack Jansen (jackjansen) * (Python committer) Date: 2002-01-18 16:01 
We should get rid of "make frameworkinstall" if you build a framework Python, and in stead have installing the framework be handled with a normal "make install".

Various people have been confused by this. Including me. More than once. :-)

"make install" for a framework build should also install a symlink in the normal (/usr/local) location, but this may be a bit difficult as the PREFIX variable (and it's dependents such as BINDIR) are forced to point into the framework when we're doing a framework build.
msg8844 - (view) Author: Jack Jansen (jackjansen) * (Python committer) Date: 2002-08-06 13:06 
Logged In: YES 
user_id=45365

I'm not going to do this after all. 'make frameworkinstall' is going to stay, and there's going to be companions 'make frameworkinstallapps' and 'make frameworkinstalltools' that install the apps and tools.

I will look into giving an error if "make install" in a framework build notices it is called outside of "make frameworkinstall".
History
Date User Action Args
2022-04-10 16:04:53adminsetgithub: 35943
2002-01-18 16:01:07jackjansencreate