Hi there! On Thu, 08 May 2008 11:47:38 +0200, Damien Sandras wrote: > Le jeudi 08 mai 2008 à 11:45 +0200, Torsten Schlabach a écrit : >> Gismo / Luca wrote: >> >>> If ekiga build-depends on >>> x264 (which, BTW, is *still* not present as a Debian package, neither in >>> non-free), ekiga itself will have to be put in non-free, which is >>> something I won't prefer. >> >> No, we don't want that I think. > > It is a pwlib plugin, so it can be packaged separately, and that > specific plugin can be put in non-free. Isn't instead an OPAL dependency? However, this won't solve anything, as far as I understood Matthias at [1]. But as a disclaimer, I haven't checked ekiga trunk lately. Please re-read the definition of the Debian categories [2]: a Debian package to be in main (thus distributed with official CDs) must build-depend only on software present in main. This means that if opal build-depends on x264 (which is, let's say, in non-free), then opal cannot be part of main. My previous statement that in this case opal (well, I wrote ekiga...) has to be put in non-free is wrong: opal can go into contrib, since opal itself is a "free package which requires [...] a non-free package for compilation". As a result, ekiga has to be put in contrib, since ekiga build-depends on opal, which isn't in main. This situation will slow ekiga adoption, which is something I don't want to see. Thx, bye, Gismo / Luca Footnotes: [1] http://mail.gnome.org/archives/ekiga-devel-list/2008-May/msg00023.html [2] http://www.debian.org/doc/debian-policy/ch-archive.html#s-sections
Attachment:
pgpkVebx5FVsY.pgp
Description: PGP signature