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: Closed
>Resolution: Fixed
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 19:02
Message:
Logged In: YES
user_id=405853
setup.py rev. 1.29 should solve the problem. It keeps PyX running in the
build directory by adjusting the relative paths. The absolute paths are
inserted in install_lib as suggested by the original patch. It hopefully will
solve the whole issue.
----------------------------------------------------------------------
Comment By: André Wobst (wobsta)
Date: 2005-02-10 18:06
Message:
Logged In: YES
user_id=405853
I see. I think, this is partially due to the fact, that its not totally trivial to
create a siteconfig.py on the fly. You need to do something like what we
already have. (In that sense its fine ... we already have it.)
OTOH I would not like to hard-code the position of the config file. Take
fink where global config files are located at /sw/etc there. And what's /
etc on Windows? (Beside the problem, that "/" is not available and
distutils fails although its not documented, but I'll work around that for
the future.)
I think it would be best to also write some adjusted version of
siteconfig.py in the build-directory. I'll just code that and then we'll see
whether it fits everybodies needs ... (or at least almost everybodies)
----------------------------------------------------------------------
Comment By: Michal Čihař (nijel)
Date: 2005-02-10 17:50
Message:
Logged In: YES
user_id=192186
Well I prefer not to have such "configuration" files, so I
try to write some kind of autodetection (and hardcode config
file in /etc). You can find this in my application Wammu and
I saw simmilar thing in imgSeek.
----------------------------------------------------------------------
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
|