OK, ran into a thorny case of a bundled lib, and after losing a couple of afternoons trying to package this sucker (iris) separately, throw in the towel that very closely meets the definition of what we currently consider a copylib.
A little background... I start out wanting to package a neat new media player, tomahawk ( https://bugzilla.redhat.com/show_bug.cgi?id=tomahawk ), found a couple of bundled libs, jreen ( https://bugzilla.redhat.com/show_bug.cgi?id=jreen ) and qtweetlib (https://bugzilla.redhat.com/show_bug.cgi?id=qtweetlib ) . so far so good.
but no, during review of jreen, it was discovered that itself bundled another item, iris. And, that several other items already in fedora also bundle it, including psi and kdenetwork(kopete).
And, my attempts to package iris separately have been met with much pain and gnashing of teeth. It's just a code snapshot, no releases, does not make a libarary in the conventional sense, and has no 'make install' target (see also https://bugzilla.redhat.com/show_bug.cgi?id=731456#c12 ). All of these things are arguably noble things to work on and strive for to make something that is packagable someday, but is far from describing the status quo.
So, here we are, with me humbly requesting that iris be granted a copylib bundling exception.
What was the blocker to shipping this as a static lib?
Thought this would be a GNU configure driven project and I could help out with the configure/Makefile patching but it's something else (qconf).... :-(
It's current buildsys doesn't provide a lib (static or otherwise), that's part of the problem. Another is that all iris-consuming apps would then require patching (but that part would be easier, admittedly).
I've given rdieter an iris package that generates pkgconfig files and shared libraries, so I'm closing this request out.
to comment on this ticket.