[Bug 186919] Review Request: eric: Python IDE

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: eric: Python IDE


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=186919


tibbs at math.uh.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tibbs at math.uh.edu




------- Additional Comments From tibbs at math.uh.edu  2006-06-21 13:33 EST -------
OK, this builds in mock on x86_64, development.  First thing I see is an empty
debuginfo package, because this is an arch-dependent package that doesn't seem
to have any binaries.  Can this truly not be noarch?  

There's also this:
E: eric no-binary

The a whole pile of
E: eric non-executable-script /usr/lib64/python2.4/site-packages/eric3/eric3.py 0644
which are caused by these modules erroneously all starting with a shebang line.
 In the past folks have just removed such lines.

Then there are a few of these:
W: eric non-executable-in-bin /usr/bin/gen_sip_api.pyo 0644
W: eric non-executable-in-bin /usr/bin/gen_sip_api.pyc 0644
W: eric non-executable-in-bin /usr/bin/gen_python_api.pyo 0644
W: eric non-executable-in-bin /usr/bin/gen_python_api.pyc 0644

RPM will compile and optimize every single .py file it finds, even in bindir,
which is obviously a bug but it seems isn't going to be fixed.  I suggest either
deleting these files or %exclude'ing them, preferably the former in case rpm
gets fixed to stop generating these in the future.

Also, this rpm behavior means that you will get .pyo files everywhere even if
you don't ask for it, so you'll need to %ghost them all.  Unfortunately this
considerably complicates the %files list.

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.