On 01/13/2012 06:20 AM, Orcan Ogetbil wrote:
On Fri, Jan 13, 2012 at 12:08 AM, Ralf Corsepius wrote:
On 01/13/2012 05:49 AM, Orcan Ogetbil wrote:
I have a grey-area issue. The new version of the clementine player
comes bundled with 3rd party source files: sha2 , echoprint-codegen
There are no licensing issues. Unfortunately, neither of the two
upstreams provide their source files as libraries. From the
descriptions in their webpages  and , they seem to me as "take
this code and use it in your project as you wish".
The question is, how do you think this would play with our guidelines?
I don't see anything unusal with both of these packages - Am I missing
IMO, these should be packaged as "ordinary packages".
Can you define "ordinary packages"?
Well, I don't see anything unusal with these packages, which would
require them to be copylibs.
To me, they just seem to lack a built-in infrastructure to "build +
install" them. This is not unusal (esp. with packages originating from
an academic background).
Should I write a Makefile or a
shell script and turn the source files into shared libraries with some
random sonames, and patch clementine to use these libraries?
More or less yes. You would not necessarily have "to write Makefiles"
and "to add shared libs", but something along these lines.
packaging mailing list