IOhannes m zmoelnig
zmoelnig at iem.at
Mon Jan 17 15:07:44 UTC 2011
-----BEGIN PGP SIGNED MESSAGE-----
out of curiosity: what is the 2nd-best practice for packages on multiple
imagine i have a package "foo".
upstream has a lot of build-dependencies, some of which are "optional".
(e.g. "bar" and "pizza")
debian happens to ship "bar", but pizza for whatever reasons, "pizza" is
not included (or more realistic: cannot be included, due to license
problems in the mozzarella code).
now in the "debian" distribution, i would like to have "Build-Depends:
foo" whereas on the "nevermind-nonfree" distro, i would like to have
"Build-Depends: foo, pizza"
afaik debian/control cannot handle such things directly (nor should it,
otoh, i think it would be nice to be able to handle such things in a
centralized repository (like pkg-multimedia), in order to keep duplicate
afforts at a minimum.
given that this group includes debian- and ubuntu-maintainers (and
probably other distros which i fail to enumerate), i guess this has been
discussed and solved somehow.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3636 bytes
Desc: S/MIME Cryptographic Signature
More information about the pkg-multimedia-maintainers