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.

Author ronaldoussoren
Recipients Amos.Anderson, julians37, khinsen, phyreman, ronaldoussoren
Date 2010-05-06.05:30:44
SpamBayes Score 2.8040575e-05
Marked as misclassified No
Message-id <1273123847.97.0.761723388664.issue3646@psf.upfronthosting.co.za>
In-reply-to
Content
Installing a framework anywhere but a reasonably standard location doesn't work. You should try to build with "--enable-framework=$SOMEPREFIX/Library/Frameworks". Applications then get installed in "$SOMEPREFIX/Applications" and command-line tools in "$SOMEPREFIX/bin". When SOMEPREFIX is /Library or /System/Library items get installed in the usual location (but don't install into /System/Library unless you are Apple).

Supporting an arbitrary framework prefix would require a clear definition on what to do with Application bundles and command-line tools and I don't have enough of a need for that to start thinking about that.
History
Date User Action Args
2010-05-06 05:30:48ronaldoussorensetrecipients: + ronaldoussoren, khinsen, julians37, phyreman, Amos.Anderson
2010-05-06 05:30:47ronaldoussorensetmessageid: <1273123847.97.0.761723388664.issue3646@psf.upfronthosting.co.za>
2010-05-06 05:30:44ronaldoussorenlinkissue3646 messages
2010-05-06 05:30:44ronaldoussorencreate