sharing code between packages

forum::für::umläute zmoelnig at umlaeute.mur.at
Mon May 26 15:48:48 UTC 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 2014-05-21 14:28, Sebastian Ramacher wrote:
> Hi
> 
> On 2014-05-21 13:34:41, "IOhannes m zmölnig (Debian/GNU)" wrote:
>> now i'm wondering what's the best way to bring both the
>> application and the library into Debian. the main obstacle is
>> obviously the code copy.
> 
> I think the best option would be to get both upstream's to merge
> the projects. ;)

obviously.
i wil be able to talk to upstreamA in person in the next week.
maybe i can convince him.

> 
> But anyway, multiple upstream tarballs are an option. They are not
> that difficult. Just be careful with naming the additional
> tarballs. If need help to get started with multiple tarballs, just
> let me know
> 
> And if you want to look at an example: I'm using them for zathura. 
> Upstream provides separate tarballs for the application and one for
> each plugin. In the zathura source package, I combine them using
> 3.0's multiple upstream tarball support.
> 
> The only problem I had was git-buildpackage and pristine-tar. I
> haven't found a way to import multiple upstream tarballs with
> git-import-orig. (This might be fixed already. I haven't looked
> into that in more detail since implementing this in zathura two
> years ago. If you find a way, please let me know.)

thanks for the offer.
i'd *rather* have good integration with gbp and pristine-tar.

> 
> Another option would be to provide a pureaudio-source binary
> package from pureaudio. You could Build-Depend on it in the library
> package. There are some packages in the archive that provide
> -source packages: gdb, gcc, etc.

good point. seems to be ugly an ugly solution :-)

fgamsdr
IOhannes

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQIcBAEBCAAGBQJTg2JVAAoJELZQGcR/ejb4FQIP/RABIyi225KUyaD49SNzGU44
epNsRLhz+Jmw6tLTWoDwv63KnAUAuZrpSYCrnolebYbu3ehL0XpF9uiml1Tex9KY
MCCvtTmsLg2Y7SXgnbyeYAFKXAciPt33XJX0FEw4qhWEHPuIpnqDiezE3dh9JzNH
VnY0hIHMnsNw2oYqTELaopMtSSP448vb04M5VCtJtpP/qcWog+UD/zSHRozZvNAu
uUk8fAGKnZve974tArNQfNxrpFMgge23iUtATfFSyR8QPMmudWZ6JUWe3u10z0RE
mCMztTnCTJY93z9Dv4X1ud2+7l3Bbfzih10wSQhKzoEH2vgywAVY328Y5ZEnPauk
hO1TGypKqRMtapX5n9bjoHSFmXUZyxncZAa33wF8u9BYl9se46IBwPZNGz4N7SV6
erPEZ0axpAjyDCR0lJ3/qAkN8J5Nl+I8FvO/Q+EkIC54Jb5gBK8W71ShbUYAOUUJ
Z/8VJYjBcF9z9E1vF8K6AvVxcdiLR3JPt2uKetH1/5JELaWyC8yxYdmYoZDM0oCr
Pc8b69lESM8EDj4+FnoqStMgsjPF7oXUJImAIDTn5hnrYBIvSK+w4iCjas2NENUb
e45pCjdznFYelKIdKS5gQt2RoY9+8g/yx9d63IqOESYtlpdsYQKl/4/ZSbiPXk2F
H6FNqV+8Gh4KLvQwgbO+
=4G4P
-----END PGP SIGNATURE-----



More information about the pkg-multimedia-maintainers mailing list