|
From: SourceForge.net <no...@so...> - 2005-02-10 16:36:59
|
Bugs item #1120100, was opened at 2005-02-10 16:31 Message generated for change (Comment added) made by wobsta You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=442886&aid=1120100&group_id=45430 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Michal Čihař (nijel) Assigned to: Nobody/Anonymous (nobody) Summary: Fails to build under non-root Initial Comment: setup.py build should not require root, however it attempts to write to /usr/share/pyx: + python setup.py build running build running build_py running install_data creating /usr/share/pyx error: could not create '/usr/share/pyx': Permission denied error: Bad exit status from /var/tmp/rpm-tmp.18551 (%build) Attached patch changes way when siteconfig.py is written. ---------------------------------------------------------------------- >Comment By: André Wobst (wobsta) Date: 2005-02-10 17:36 Message: Logged In: YES user_id=405853 Ok. My idea was to already create the final version of siteconfig.py in the build directory. But you're right that this is too much burden to cover for a build command. build_py should better not depend on install_data. Anyway I like your suggestion in modifying install_lib instead of build_py and replace siteconfig.py right after the copy_tree performed by install_lib's install method. But why not keep the dependance on a modified version of install_data? I think its better to keep the path calculation for siteconfig.py in install_data. Any objections? BTW there is another problem with this new version (your and mine as well): PyX does not run from the build directory anymore, since there is no build_data to copy the data into the build directory and the siteconfig.py from PyX referes to some relative paths. Should we fix that? I'm not sure whether its needed to have a running version in the build directory, but that's something I do not yet like too much. We could *additionally* fix the siteconfig.py by our own build_py command but keep it to be relative paths. Or implement a build_data ... ?! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=442886&aid=1120100&group_id=45430 |