Bug 1121774

Created attachment 919755 [details]
python3-pyside-1.2.2-10.2.src.rpm

Created attachment 919756 [details]
python3-pygame-1.9.2a0-15.f21.src.rpm

Created attachment 919757 [details]
smpeg-0.4.5-2.1.src.rpm

Created attachment 919760 [details]
python3-pyside.spec

Created attachment 919761 [details]
smpeg.spec

Created attachment 919762 [details]
kivy.spec

Created attachment 919763 [details]
pygame.spec

smpeg not necessary, if smpeg is encumbered it may be dropped.

[Kyvy] ---requires--> [pygame] ---requires--> [pyside] ---requires--> [qt]

Kivy is a platform independent multitouch natural user interface framework [8]
PySide is a Python binding of the cross-platform GUI toolkit Qt [5]

Pygame was built to replace pySDL after its development stalled [6]

smpeg may be deprecated [1] SMPEG provided MPEG-layer-1 [2] it may be patent encumbered though they may be set to expire, one of these years [3] It may need careful invetigation [4]

The smpeg-devel package seems to be required only for building because pygame-comilation looks for smpeg-config. It probably not really. setting environment variable SDL_VIDEODRIVER to dummy is one suggested option[7]

pygame will build even without smpeg-config

[1] http://fedoraproject.org/wiki/User:Peter/Disabled_applications
[2] http://en.wikipedia.org/wiki/SMPEG
[3] http://www.kuro5hin.org/story/2008/7/18/232618/312
[4] http://scratchpad.wikia.com/wiki/MPEG_patent_lists
[5] http://en.wikipedia.org/wiki/PySide
[6] http://en.wikipedia.org/wiki/Pygame
[7] https://code.google.com/p/gheat/wiki/PygameInstallation [7]
[8] http://en.wikipedia.org/wiki/Kivy

even if built with smpeg the rpm does not have smpeg depdency so the devel package can be uninstalled.

A snip from build of pygame without smpeg 

<snip>
Hunting dependencies...
/bin/sh: smpeg-config: command not found
/bin/sh: smpeg-config: command not found
/bin/sh: smpeg-config: command not found
WARNING: "smpeg-config" failed!
SDL     : found 1.2.15
FONT    : found
IMAGE   : found
MIXER   : found
SMPEG   : not found
PNG     : found
JPEG    : found
SCRAP   : found
PORTMIDI: found
PORTTIME: found
AVFORMAT: found
SWSCALE : found
FREETYPE: found 2.5.3
</snip>
but compilation does proceed and completes making rpms


conclusion if smpeg is encumbered it may be dropped.

I see that nobody answered this so far, sorry for that.

On the other hand I have to say that this bug report is really bad to work with as you submitted four reports in a single issue. I recommend reading other review requests (and possibly also http://fedoraproject.org/wiki/Package_Review_Process) to get an impression how a more manageable review request looks like.

I'd like to encourage you to present your changes in bug 1045780 if you're still interested. Some small issues about your pyside request:
 - attachment 919755 [details] (labelled as "python3-pyside-1.2.2-10.2.src.rpm") actually contains pygame.
 - The pyside spec has several glitches (python3 packages as unconditional BuildRequires, change log entry too brief)

Created attachment 949601 [details]
python3-pyside-1.2.2-10.2.src.rpm [comment 10]


corrected pyside srpm attached.

yes Felix, I jsut wouldn't know all that, or as a matter of a normal day get into the level of detail that involves packaging. I'm just hoping what I do is a sufficient starting point for a person with more packaging knowledge and an interest in pyside.

(In reply to Ganapathi Kamath from comment #11)
> yes Felix, I jsut wouldn't know all that, or as a matter of a normal day get
> into the level of detail that involves packaging. I'm just hoping what I do
> is a sufficient starting point for a person with more packaging knowledge
> and an interest in pyside.

I appreciate your interest in packaging and I'd like to encourage you learn more about it so you can help improving the Fedora packaging base.
However I have to say that packaging pyside for Python 3 requires some intermediate level of packaging knowledge (multiple packages involved, shiboken must link against Python 3, both pyside and shiboken contain very complex code) and unfortunately your spec file does not address any of these more complicated issues (I'd love to be wrong about this though!).

Maybe you could startstart co-maintaining a simple package which you use personally (e.g. for Python) to learn how to handle the "routine" tasks.

This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.