Re: d-m.o dependency tree
2012/2/10 Fabian Greffrath fab...@greffrath.com: Am 09.02.2012 16:49, schrieb Sebastian Dröge: Not obsoleted (yet). faac supports 1-6 channels and the main, lc, ssr and ltp profiles. vo-aacenc only supports 1-2 channels and the lc profile. OK, so it's good enough for the usual CD ripping. The current gnome-media-profiles still uses the faac plugin, right? ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers Whatever became of this? Should faac be uploaded to non-free at least for now? -- ~ Andres ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: d-m.o dependency tree
Am 09.02.2012 18:37, schrieb Reinhard Tartler: Aah, I didn't get this point yesterday on the phone. Right, so porting the faac frontend to libavformat would allow us to drop the internal libmp4v2 copy. Good idea. Yes, but it would still remain non-free because of the reference implementation used in libfaac! Thus we should try to also port it to vo-aacenc. Of course, the result won't be the well-known FAAC anymore, but least would be something we could offer those programs that still rely on the FAAC CLI frontend. I think we need FAAC CLI frontend with (1) vo-aacenc instead of libfaac (non-free) and (2) libavformat instead of libmp4v2 (MPL). We should call it other than FAAC then, though. ;) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: d-m.o dependency tree
Am 09.02.2012 17:34, schrieb Alessio Treglia: Do you mean FAAC links against libmp4v2? If so, we could try to make it rely on a dlopen() based mechanism. For the initial upload to Debian we could simply configure --without-mp4v2. BTW, the library is not affected, only the CLI frontend. I assume it will be OK to ship both sources in the same tarball as long as they are not linked together? OTOH, I am still not sure what happens when you link GPL and MPL code. I have read http://www.gnu.org/licenses/license-list.en.html#MPL-2.0 but did not understand a word. :/ ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: d-m.o dependency tree
On 12-02-10 at 09:19am, Fabian Greffrath wrote: Am 09.02.2012 17:34, schrieb Alessio Treglia: Do you mean FAAC links against libmp4v2? If so, we could try to make it rely on a dlopen() based mechanism. For the initial upload to Debian we could simply configure --without-mp4v2. BTW, the library is not affected, only the CLI frontend. I assume it will be OK to ship both sources in the same tarball as long as they are not linked together? OTOH, I am still not sure what happens when you link GPL and MPL code. I have read http://www.gnu.org/licenses/license-list.en.html#MPL-2.0 but did not understand a word. :/ Then ask for help interpreting it at d-legal@ :-) - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: d-m.o dependency tree
On Fri, Feb 10, 2012 at 9:19 AM, Fabian Greffrath fab...@greffrath.com wrote: For the initial upload to Debian we could simply configure --without-mp4v2. BTW, the library is not affected, only the CLI frontend. I assume it will be OK to ship both sources in the same tarball as long as they are not linked together? OTOH, I am still not sure what happens when you link GPL and MPL code. I have read http://www.gnu.org/licenses/license-list.en.html#MPL-2.0 but did not understand a word. :/ Regarding MPL-2.0, gnu.org explicitly states [1]: This is a free software license. Section 3.3 provides indirect compatibility between this license and the GNU GPL version 2.0, the GNU LGPL version 2.1, the GNU AGPL version 3.0, and all later versions of those licenses. [...] And regarding MPL-1.1, it says [2]: This is a free software license which is not a strong copyleft; unlike the X11 license, it has some complex restrictions that make it incompatible with the GNU GPL. That is, a module covered by the GPL and a module covered by the MPL cannot legally be linked together. We urge you not to use the MPL for this reason. [...] So, if the faac's CLI frontend links against mp4v2 yes, it is affected by a serious issue and we must disable the offending linking flag. Otherwise, no, it isn't. www.gnu.org's website is often extremely useful for searching information about compatibility between GNU's licenses and the-rest-of-the-world. [1] http://www.gnu.org/licenses/license-list.en.html#MPL [2] http://www.gnu.org/licenses/license-list.en.html#MPL-2.0 -- Alessio Treglia | www.alessiotreglia.com Debian Developer | ales...@debian.org Ubuntu Core Developer | quadris...@ubuntu.com 0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: d-m.o dependency tree
Am 10.02.2012 09:49, schrieb Alessio Treglia: And regarding MPL-1.1, it says [2]: This is a free software license which is not a strong copyleft; unlike the X11 license, it has some complex restrictions that make it incompatible with the GNU GPL. That is, a module covered by the GPL and a module covered by the MPL cannot legally be linked together. We urge you not to use the MPL for this reason. [...] Ah, I have mixed up MPL-2.0 and MPL-1.1. libmp4v2 is licensed under the latter. So, if the faac's CLI frontend links against mp4v2 yes, it is affected by a serious issue and we must disable the offending linking flag. Otherwise, no, it isn't. That's a clear statement, thanks! No need for -devel this time. ;) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: d-m.o dependency tree
On 12-02-10 at 09:59am, Fabian Greffrath wrote: Am 10.02.2012 09:49, schrieb Alessio Treglia: And regarding MPL-1.1, it says [2]: This is a free software license which is not a strong copyleft; unlike the X11 license, it has some complex restrictions that make it incompatible with the GNU GPL. That is, a module covered by the GPL and a module covered by the MPL cannot legally be linked together. We urge you not to use the MPL for this reason. [...] Ah, I have mixed up MPL-2.0 and MPL-1.1. libmp4v2 is licensed under the latter. So, if the faac's CLI frontend links against mp4v2 yes, it is affected by a serious issue and we must disable the offending linking flag. Otherwise, no, it isn't. That's a clear statement, thanks! No need for -devel this time. ;) ...or -legal ;-) - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: d-m.o dependency tree
Am 09.02.2012 16:49, schrieb Sebastian Dröge: Not obsoleted (yet). faac supports 1-6 channels and the main, lc, ssr and ltp profiles. vo-aacenc only supports 1-2 channels and the lc profile. OK, so it's good enough for the usual CD ripping. The current gnome-media-profiles still uses the faac plugin, right? ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: d-m.o dependency tree
On Thu, Feb 9, 2012 at 4:19 PM, Fabian Greffrath fab...@greffrath.com wrote: Dear team, I have created a d-m.o dependency tree that shows all packages offered at d-m.o with dependencies that cannot get satisfied by packages from Debian sid. I do not consider it complete Ah-ah! Great idea Fabian! gpac has been uploaded, let's see what happens :) -- Alessio Treglia | www.alessiotreglia.com Debian Developer | ales...@debian.org Ubuntu Core Developer | quadris...@ubuntu.com 0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: d-m.o dependency tree
On Do, 2012-02-09 at 16:19 +0100, Fabian Greffrath wrote: [...] - libfaac0 (contains non-free files, probably obsoletet by vo-aacenc) Not obsoleted (yet). faac supports 1-6 channels and the main, lc, ssr and ltp profiles. vo-aacenc only supports 1-2 channels and the lc profile. signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: d-m.o dependency tree
2012/2/9 Sebastian Dröge sl...@circular-chaos.org: On Do, 2012-02-09 at 16:19 +0100, Fabian Greffrath wrote: [...] - libfaac0 (contains non-free files, probably obsoletet by vo-aacenc) Not obsoleted (yet). faac supports 1-6 channels and the main, lc, ssr and ltp profiles. vo-aacenc only supports 1-2 channels and the lc profile. That's a good point. Thanks for pointing this out. In the telephone call I had with Fabian yesterday we agreed that the best way to handle this is probably to a) get faac into debian/non-free, b) forward-port the old patch to libavcodec to dlopen() it and c) port applications to libavcodec with faac. -- regards, Reinhard ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: d-m.o dependency tree
Am 09.02.2012 17:16, schrieb Reinhard Tartler: In the telephone call I had with Fabian yesterday we agreed that the best way to handle this is probably to a) get faac into debian/non-free, b) forward-port the old patch to libavcodec to dlopen() it and c) port applications to libavcodec with faac. And d) for bonus points (and software using the command line frontend), create a CLI for vo-aacenc that is command line compatible to the FAAC frontend and uses libavformat for mp4 muxing (FAAC currently uses libmp4v2, which we might need to disable before even attampting to get it into Debian). ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: d-m.o dependency tree
On Thu, Feb 9, 2012 at 5:31 PM, Fabian Greffrath fab...@greffrath.com wrote: (FAAC currently uses libmp4v2, which we might need to disable before even attampting to get it into Debian). Do you mean FAAC links against libmp4v2? If so, we could try to make it rely on a dlopen() based mechanism. -- Alessio Treglia | www.alessiotreglia.com Debian Developer | ales...@debian.org Ubuntu Core Developer | quadris...@ubuntu.com 0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: d-m.o dependency tree
On Thu, Feb 9, 2012 at 5:31 PM, Fabian Greffrath fab...@greffrath.com wrote: Am 09.02.2012 17:16, schrieb Reinhard Tartler: In the telephone call I had with Fabian yesterday we agreed that the best way to handle this is probably to a) get faac into debian/non-free, b) forward-port the old patch to libavcodec to dlopen() it and c) port applications to libavcodec with faac. And d) for bonus points (and software using the command line frontend), create a CLI for vo-aacenc that is command line compatible to the FAAC frontend and uses libavformat for mp4 muxing (FAAC currently uses libmp4v2, which we might need to disable before even attampting to get it into Debian). Aah, I didn't get this point yesterday on the phone. Right, so porting the faac frontend to libavformat would allow us to drop the internal libmp4v2 copy. Good idea. -- regards, Reinhard ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
