Bugzilla Bug 24057

Hi, 
 
Here's an ebuild for CheeseTracker 0.8.0. There are, however, problems ... 
 
First, the ebuild depends on scons-0.14. Someone has submitted an ebuild for this, but 
is not in the portage tree yet. See the 'bug depends on' field. 
 
Secondly, there are sandbox problems, reproducible always as follows: 
 
1. emerge scons 
2. emerge cheesetracker 
 
SCons is Python-based, and it seems that it tries to recompile itself the first time it is 
used after installation. It tries to write to many .pyc files in /usr/lib/scons/SCons, and 
this fails unless it has root access. This only happens the first time SCons is used (and 
succeeds); the following sequence does not generate any errors: 
 
1. emerge scons 
2. FEATURES=-sandbox emerge cheesetracker 
3. emerge cheesetracker 
 
My system has python-2.2.3 on it. 
 
I have no idea how this should be fixed, but then I know very little about Python or 
SCons. We may need to contact the SCons developers for advice.

Created an attachment (id=14233) [details]
The ebuild

Ugh. Sorry about the evil word wrapping. I got an error when submitting the
ebuild 
too (although it worked). That's the last time I use Konqueror for anything
important ... 

Hi, I'm the SCons project leader, and got notification of this bug because I
also submitted the depends-on bug about upgrading SCons.

Creating the .pyo files should ideally be done as part of the installation.  My
guess is it should then be something in the .ebuild itself, but this is all new
to me.  The .ebuild file I submitted in the depends-on bug for SCons 0.14 is
essentially cut-and-paste from the .ebuild file I already found in gentoo for
SCons 0.07.  If someone can point me to other examples I can look at of Python
apps that create their .pyo files as part of the installation, I'll gladly
update and re-submit.

As far as I could tell at the time, SCons was trying to replace existing .pyc
files with new ones, presumably derived from the .py files in the same place.
The .py and .pyc had identical (or very close) modification times on them.
Presumably either Python or SCons determined that the .pyc files MIGHT be out
of date, and wanted to update them. No .pyo files existed before or afterwards;
only .py and .pyc files.

*** Bug 8858 has been marked as a duplicate of this bug. ***

Works fine for 0.9.0 (just released today) as well!

Good for 0.9.1 as well.

I'll take a look at this... Would you be able to create a patch so
FEATURES=-sandbox is not needed?

Disabling sandbox shouldn't be neccesary anymore as I fixed dev-util/scons
yesterday - see bug 42660.

in portage.