Re: faad2 and faac
FYI it's not 10bit it just builds the digital radio Mondiale versions of the libraries with unique names. Useful to us, but niche. Julian > On 11 Dec 2014, at 14:43, Jonas Smedegaard wrote: > > Quoting Fabian Greffrath (2014-12-11 15:20:33) >> Am Donnerstag, den 11.12.2014, 14:38 +0100 schrieb Jonas Smedegaard: >>> Sure, not all do that, but also not all use unstable, so similar >>> argument as used for not uploading to experimental during freeze can be >>> used for not uploading to unstable until close before freeze. >> >> I generally do intermediate uploads to experimental if I see use in >> it, e.g. see flac 1.3.1. But in the case of faac/faad2, apart from >> general packaging clean up, the only relevant changes were the ones >> requested by and introduced for the DReaM people. > > Ah, the 10bit support. Sorry, I reacted without reading through the > thread - makes fine sense to me to postpone that! > > Sorry for the noise, > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private ___ 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: faad2 and faac
Quoting Fabian Greffrath (2014-12-11 15:20:33) > Am Donnerstag, den 11.12.2014, 14:38 +0100 schrieb Jonas Smedegaard: >> Sure, not all do that, but also not all use unstable, so similar >> argument as used for not uploading to experimental during freeze can be >> used for not uploading to unstable until close before freeze. > > I generally do intermediate uploads to experimental if I see use in > it, e.g. see flac 1.3.1. But in the case of faac/faad2, apart from > general packaging clean up, the only relevant changes were the ones > requested by and introduced for the DReaM people. Ah, the 10bit support. Sorry, I reacted without reading through the thread - makes fine sense to me to postpone that! Sorry for the noise, - 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: 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: faad2 and faac
Am Donnerstag, den 11.12.2014, 14:38 +0100 schrieb Jonas Smedegaard: > Sure, not all do that, but also not all use unstable, so similar > argument as used for not uploading to experimental during freeze can be > used for not uploading to unstable until close before freeze. I generally do intermediate uploads to experimental if I see use in it, e.g. see flac 1.3.1. But in the case of faac/faad2, apart from general packaging clean up, the only relevant changes were the ones requested by and introduced for the DReaM people. Cheers, Fabian ___ 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: faad2 and faac
Quoting Fabian Greffrath (2014-12-11 11:02:08) > Am Dienstag, den 11.11.2014, 10:31 +0100 schrieb Fabian Greffrath: >> The package revisions will be faad2 (2.7-9) and faac (1.28-7). I will >> upload them as soon as my GPG key is added to the debian-maintainers >> keyring or after the freeze -- whatever comes first. ;) > > Yes, I've said that. Well, I am a DM now and still haven't uploaded > the packages. Why? The reason is that due to the testing freeze, it > would be wrong to upload it to unstable now. It would have to go to > experimental instead. But, for the changes to actually take > Debian-wide effect I would have to upload it to unstable again, > anyway, when the freeze is over. > > So, I thought I'd save us one additional upload at the cost of no > intermediate testing of the packages in experimental. I hope you cope > with me. Please reconsider: Some do cherry-pick from experimental. Sure, not all do that, but also not all use unstable, so similar argument as used for not uploading to experimental during freeze can be used for not uploading to unstable until close before freeze. - 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: 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: faad2 and faac
Hi Fabian. That's just what I was expecting. I'm going to wait until the new libFaad is in unstable before I ask the hamradio folks to upload dream. That gives me time to make it work properly with some new GUI libraries. Julian > On 11 Dec 2014, at 10:02, Fabian Greffrath wrote: > > Am Dienstag, den 11.11.2014, 10:31 +0100 schrieb Fabian Greffrath: >> The package revisions will be faad2 (2.7-9) and faac (1.28-7). I will >> upload them as soon as my GPG key is added to the debian-maintainers >> keyring or after the freeze -- whatever comes first. ;) > > Yes, I've said that. Well, I am a DM now and still haven't uploaded the > packages. Why? The reason is that due to the testing freeze, it would be > wrong to upload it to unstable now. It would have to go to experimental > instead. But, for the changes to actually take Debian-wide effect I > would have to upload it to unstable again, anyway, when the freeze is > over. > > So, I thought I'd save us one additional upload at the cost of no > intermediate testing of the packages in experimental. I hope you cope > with me. > > Best regards, > > Fabian > > ___ 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: faad2 and faac
Am Dienstag, den 11.11.2014, 10:31 +0100 schrieb Fabian Greffrath: > The package revisions will be faad2 (2.7-9) and faac (1.28-7). I will > upload them as soon as my GPG key is added to the debian-maintainers > keyring or after the freeze -- whatever comes first. ;) Yes, I've said that. Well, I am a DM now and still haven't uploaded the packages. Why? The reason is that due to the testing freeze, it would be wrong to upload it to unstable now. It would have to go to experimental instead. But, for the changes to actually take Debian-wide effect I would have to upload it to unstable again, anyway, when the freeze is over. So, I thought I'd save us one additional upload at the cost of no intermediate testing of the packages in experimental. I hope you cope with me. Best regards, Fabian ___ 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: faad2 and faac
Ah, the email title confused me - I thought you were talking about faad/faac. But I don't mind tweaking this one. I'll take a look tomorrow. From: Fabian Greffrath To: Julian Cable Cc: Reinhard Tartler ; Debian Multimedia Maintainers Sent: Saturday, 15 November 2014, 11:26 Subject: Re: faad2 and faac Am Samstag, den 15.11.2014, 10:01 + schrieb Julian Cable: > sure, i'll put something together. Thanks! I have already commited a stub manpage. It could use some proof-reading and improved wording, I am not a native speaker: http://anonscm.debian.org/cgit/pkg-multimedia/x264.git/diff/debian/x264-10bit.1?id=7344bef808740be6b848afa0ed61b70b32519ef1 - Fabian ___ 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: faad2 and faac
Am Samstag, den 15.11.2014, 10:01 + schrieb Julian Cable: > sure, i'll put something together. Thanks! I have already commited a stub manpage. It could use some proof-reading and improved wording, I am not a native speaker: http://anonscm.debian.org/cgit/pkg-multimedia/x264.git/diff/debian/x264-10bit.1?id=7344bef808740be6b848afa0ed61b70b32519ef1 - Fabian ___ 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: faad2 and faac
sure, i'll put something together. From: Fabian Greffrath To: Reinhard Tartler Cc: Debian Multimedia Maintainers ; Julian Cable Sent: Friday, 14 November 2014, 9:19 Subject: Re: faad2 and faac Am Freitag, den 14.11.2014, 09:28 +0100 schrieb Fabian Greffrath: > Sigh, we will need a manpage for this. Any volunteers? Whatever, done and commited. - Fabian ___ 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: faad2 and faac
Am Freitag, den 14.11.2014, 09:28 +0100 schrieb Fabian Greffrath: > Sigh, we will need a manpage for this. Any volunteers? Whatever, done and commited. - Fabian ___ 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: faad2 and faac
Am Donnerstag, den 13.11.2014, 08:55 -0500 schrieb Reinhard Tartler: > Julien, Fabian, do you think this would be helpful to have in the x264 > package under /usr/bin? Sigh, we will need a manpage for this. Any volunteers? - Fabian ___ 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: faad2 and faac
Makes perfect sense. Julian > On 13 Nov 2014, at 15:38, Fabian Greffrath wrote: > > Am Donnerstag, den 13.11.2014, 14:54 + schrieb Julian Cable: >> different name. There are more applications that use x264. I think the >> discussion could be had with them. > > Oh, we had this discussion in the past. Unfortunately, it is currently > impossible for the x264 library to support both bit widths. It's an > either-or decision that has to be taken at build-time, similar to the > current state of the faad library. > >> command. So for x264 you might say: >> >> 10bit vlc > > That is exactly the purpuse of the short shell code that Reinhard > posted. > > Cheers, > > Fabian > > ___ 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: faad2 and faac
Am Donnerstag, den 13.11.2014, 14:54 + schrieb Julian Cable: > different name. There are more applications that use x264. I think the > discussion could be had with them. Oh, we had this discussion in the past. Unfortunately, it is currently impossible for the x264 library to support both bit widths. It's an either-or decision that has to be taken at build-time, similar to the current state of the faad library. > command. So for x264 you might say: > > 10bit vlc That is exactly the purpuse of the short shell code that Reinhard posted. Cheers, Fabian ___ 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: faad2 and faac
I think in both these cases it would be better with one library that supported both feature sets. In the case of faac/faad2 this was the intent but the DRM code broke the normal code and there is no development resource to recombine them. The DRM version is only used by a few applications that can be coded to use a library with a different name. There are more applications that use x264. I think the discussion could be had with them. The other big use of LD_LIBRARY_PATH I'm aware of is the socksify command which overrides the networking shared library. It doesn't set the path and get out of the way, it's used as a prefix to every command. So for x264 you might say: 10bit vlc Julian > On 13 Nov 2014, at 14:13, Fabian Greffrath wrote: > > Am Donnerstag, den 13.11.2014, 08:55 -0500 schrieb Reinhard Tartler: >> Julien, Fabian, do you think this would be helpful to have in the x264 >> package under /usr/bin? > > Looks good to me, let's just add it. > > - Fabian > > ___ 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: faad2 and faac
Am Donnerstag, den 13.11.2014, 08:55 -0500 schrieb Reinhard Tartler: > Julien, Fabian, do you think this would be helpful to have in the x264 > package under /usr/bin? Looks good to me, let's just add it. - Fabian ___ 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: faad2 and faac
On Mon, Nov 10, 2014 at 5:38 AM, Fabian Greffrath wrote: > Hey Julian, > > I've just tested your approach with the faad2 package and it works just > as expected. I'll add the necessary changes to the Debian packaging soon > [tm]. But please note that we are not in a hurry: testing is currently > frozen and I see zero chance that faad2 will get a freeze exception with > a change as intrusive as this. > > BTW, I have decided to put the renamed library into the regular libfaad2 > package. It has a different name and weights only ~250kB. So, you only > need to take care to link your own application against the correct > library name. > > @team: Does anyone remember why we put the 10bit-libx264 into a > subdirectory instead of renaming the library? One has to use LD_PRELOAD > magic, anyway, to use it. According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667573#29, setting LD_LIBRARY_PATH would do just fine. According to the buglog, I proposed the idea of shipping a shell wrapper that sets that for you, but it seems I never got around doing is. I have attached the shell wrapper that I had to this email. it seems to even work as expected: ./x264-10bit ldd /usr/bin/x264 | grep libx264.so libx264.so.142 => /usr/lib/x86_64-linux-gnu/x264-10bit/libx264.so.142 (0x7fd32d4e7000) Julien, Fabian, do you think this would be helpful to have in the x264 package under /usr/bin? -- regards, Reinhard x264-10bit Description: Binary data ___ 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: faad2 and faac
That all sounds perfect. Many thanks. Julian > On 11 Nov 2014, at 09:31, Fabian Greffrath wrote: > > Am Montag, den 10.11.2014, 13:28 + schrieb Julian Cable: >> Hi Fabian. The sourceforge upstream project have also already >> committed the changes and tagged them but don't know when/if they will >> do releases. So instead of the patch you could import an upstream vcs >> tarball. > > I have seen that with surprise! However, as long as our Debian package > does not fall back too far from upstream development (which is, ahem, > unexpected) I am reluctant to package an unreleased VCS snapshot. > >> If we can agree on a release version number I can put it into the >> Debian dream package as a >= dependency and when you are ready we can >> package consistently. That will be a great help to anyone trying to >> run Dream on Debian and derivatives. > > The package revisions will be faad2 (2.7-9) and faac (1.28-7). I will > upload them as soon as my GPG key is added to the debian-maintainers > keyring or after the freeze -- whatever comes first. ;) > > Regarding your dream package: Please add "Build-Depends: libfaad-dev (>= > 2.7-9~)" to the debian/control file. If you make sure to link against > the correct library (i.e. the one with _drm in its name), the binary > package dependencies will be chosen appropriately. > Since faac is non-free, your package must not have a Depends or > Recommends relation with it. So, what remains is "Suggests: libfaac0". > Since weak dependencies, i.e. Recommends and Suggests, cannot be > versioned, you need another measure to make sure that the right libfaac0 > package revision gets installed. Thus, please add an additional "Breaks: > libfaac0 (<< 1.28-7~)". This will upgrade already installed revisions of > this package, that do not contain the libfaac_drm library, and will also > prevent lower package revisions to get installed as long as the dream > package is installed. > > Hope that helps. > > Fabian > > >> Thanks for such quick work. >> >> Julian >> On 10 Nov 2014, at 10:38, Fabian Greffrath >>> wrote: >>> >>> Hey Julian, >>> >>> I've just tested your approach with the faad2 package and it works >> just >>> as expected. I'll add the necessary changes to the Debian packaging >> soon >>> [tm]. But please note that we are not in a hurry: testing is >> currently >>> frozen and I see zero chance that faad2 will get a freeze exception >> with >>> a change as intrusive as this. >>> >>> BTW, I have decided to put the renamed library into the regular >> libfaad2 >>> package. It has a different name and weights only ~250kB. So, you >> only >>> need to take care to link your own application against the correct >>> library name. >>> >>> @team: Does anyone remember why we put the 10bit-libx264 into a >>> subdirectory instead of renaming the library? One has to use >> LD_PRELOAD >>> magic, anyway, to use it. >>> >>> Thank you very much already! >>> >>> - Fabian >>> >>> >>> cg== >> >> ___ >> pkg-multimedia-maintainers mailing list >> pkg-multimedia-maintainers@lists.alioth.debian.org >> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers > > ___ 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: faad2 and faac
Am Montag, den 10.11.2014, 13:28 + schrieb Julian Cable: > Hi Fabian. The sourceforge upstream project have also already > committed the changes and tagged them but don't know when/if they will > do releases. So instead of the patch you could import an upstream vcs > tarball. I have seen that with surprise! However, as long as our Debian package does not fall back too far from upstream development (which is, ahem, unexpected) I am reluctant to package an unreleased VCS snapshot. > If we can agree on a release version number I can put it into the > Debian dream package as a >= dependency and when you are ready we can > package consistently. That will be a great help to anyone trying to > run Dream on Debian and derivatives. The package revisions will be faad2 (2.7-9) and faac (1.28-7). I will upload them as soon as my GPG key is added to the debian-maintainers keyring or after the freeze -- whatever comes first. ;) Regarding your dream package: Please add "Build-Depends: libfaad-dev (>= 2.7-9~)" to the debian/control file. If you make sure to link against the correct library (i.e. the one with _drm in its name), the binary package dependencies will be chosen appropriately. Since faac is non-free, your package must not have a Depends or Recommends relation with it. So, what remains is "Suggests: libfaac0". Since weak dependencies, i.e. Recommends and Suggests, cannot be versioned, you need another measure to make sure that the right libfaac0 package revision gets installed. Thus, please add an additional "Breaks: libfaac0 (<< 1.28-7~)". This will upgrade already installed revisions of this package, that do not contain the libfaac_drm library, and will also prevent lower package revisions to get installed as long as the dream package is installed. Hope that helps. Fabian > Thanks for such quick work. > > Julian > > > On 10 Nov 2014, at 10:38, Fabian Greffrath > wrote: > > > > Hey Julian, > > > > I've just tested your approach with the faad2 package and it works > just > > as expected. I'll add the necessary changes to the Debian packaging > soon > > [tm]. But please note that we are not in a hurry: testing is > currently > > frozen and I see zero chance that faad2 will get a freeze exception > with > > a change as intrusive as this. > > > > BTW, I have decided to put the renamed library into the regular > libfaad2 > > package. It has a different name and weights only ~250kB. So, you > only > > need to take care to link your own application against the correct > > library name. > > > > @team: Does anyone remember why we put the 10bit-libx264 into a > > subdirectory instead of renaming the library? One has to use > LD_PRELOAD > > magic, anyway, to use it. > > > > Thank you very much already! > > > > - Fabian > > > > > > cg== > > ___ > pkg-multimedia-maintainers mailing list > pkg-multimedia-maintainers@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers > ___ 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: faad2 and faac
Hi Fabian. The sourceforge upstream project have also already committed the changes and tagged them but don't know when/if they will do releases. So instead of the patch you could import an upstream vcs tarball. I've waited so long to do this I can wait until after the thaw! If we can agree on a release version number I can put it into the Debian dream package as a >= dependency and when you are ready we can package consistently. That will be a great help to anyone trying to run Dream on Debian and derivatives. Thanks for such quick work. Julian > On 10 Nov 2014, at 10:38, Fabian Greffrath wrote: > > Hey Julian, > > I've just tested your approach with the faad2 package and it works just > as expected. I'll add the necessary changes to the Debian packaging soon > [tm]. But please note that we are not in a hurry: testing is currently > frozen and I see zero chance that faad2 will get a freeze exception with > a change as intrusive as this. > > BTW, I have decided to put the renamed library into the regular libfaad2 > package. It has a different name and weights only ~250kB. So, you only > need to take care to link your own application against the correct > library name. > > @team: Does anyone remember why we put the 10bit-libx264 into a > subdirectory instead of renaming the library? One has to use LD_PRELOAD > magic, anyway, to use it. > > Thank you very much already! > > - Fabian > > > cg== ___ 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: faad2 and faac
Hey Julian, I've just tested your approach with the faad2 package and it works just as expected. I'll add the necessary changes to the Debian packaging soon [tm]. But please note that we are not in a hurry: testing is currently frozen and I see zero chance that faad2 will get a freeze exception with a change as intrusive as this. BTW, I have decided to put the renamed library into the regular libfaad2 package. It has a different name and weights only ~250kB. So, you only need to take care to link your own application against the correct library name. @team: Does anyone remember why we put the 10bit-libx264 into a subdirectory instead of renaming the library? One has to use LD_PRELOAD magic, anyway, to use it. Thank you very much already! - Fabian ___ 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: faad2 and faac
Oops. Sorry. Pressed the wrong button. Julian > On 10 Nov 2014, at 05:37, Fabian Greffrath wrote: > > Hi Julian, > > please don't drop the list from CC, we are discussing a team-maintained > package. > > Am Sonntag, den 09.11.2014, 03:59 -0800 schrieb Julian Cable: >> I've just asked myself the same question - I had a go at making the >> changes and it all worked fine. If we add the new libraries to the >> existing packages, there is really only a change to the Makefile.am >> and it's all done! > > I see. I would have prefered the "long" way of running "./configure > --with-drm", then "make", then rename and backup the library, "make > clean" and repeat without "--with-drm". But checking configure.in, I see > that the only difference between a build "--with-drm" and a build > without is actually the two #defines that you add, so I think your way > is even the cleaner solution. > >> I've raised tickets on the upstream projects for this but I don't know >> if Menno Bakker can make time to do a new release. It could be done as >> a Debian patch and i've made the patch files (you would need to review >> and modify the metadata in these). > > I am afraid that upstream is pretty dead now. The latest releases are > more than 5 years old, Menno is working on something different > professionally, I believe, and the latest changes I proposed on the > sourceforge bug tracker weren't even merged by himself anymore, but by > someone else (and this is even more than two years ago). > >> In my experiments I added new binary packages, but I think this is a >> bad idea. > > Why do you think so? I think this should be discussed with the team. > > - Fabian > > > ___ 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: faad2 and faac
Hi Julian, please don't drop the list from CC, we are discussing a team-maintained package. Am Sonntag, den 09.11.2014, 03:59 -0800 schrieb Julian Cable: > I've just asked myself the same question - I had a go at making the > changes and it all worked fine. If we add the new libraries to the > existing packages, there is really only a change to the Makefile.am > and it's all done! I see. I would have prefered the "long" way of running "./configure --with-drm", then "make", then rename and backup the library, "make clean" and repeat without "--with-drm". But checking configure.in, I see that the only difference between a build "--with-drm" and a build without is actually the two #defines that you add, so I think your way is even the cleaner solution. > I've raised tickets on the upstream projects for this but I don't know > if Menno Bakker can make time to do a new release. It could be done as > a Debian patch and i've made the patch files (you would need to review > and modify the metadata in these). I am afraid that upstream is pretty dead now. The latest releases are more than 5 years old, Menno is working on something different professionally, I believe, and the latest changes I proposed on the sourceforge bug tracker weren't even merged by himself anymore, but by someone else (and this is even more than two years ago). > In my experiments I added new binary packages, but I think this is a > bad idea. Why do you think so? I think this should be discussed with the team. - Fabian ___ 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: faad2 and faac
Am Samstag, den 08.11.2014, 09:29 -0800 schrieb Julian Cable: > It would be great if there could be additional binary packages built > from the source packages which installed the libfaad2_drm.so and > libfaac_drm.so files. Should be no problem. Would you prefer the additional libraries in separate packages or in the present packages? Since you plan to rename them anyway, the latter would cause no conflict (and we already so something similar with libx264). - Fabian ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
faad2 and faac
Hi, I'm currently packaging Dream (drm.sourceforge.net) for Debian. Dream uses faad2 and faac for AAC but it needs special versions of the libraries built with the DRM symbol defined. We have instructions on the Dream wiki: http://drm.sourceforge.net/wiki/index.php/Building_on_apt_based_distros It would be great if there could be additional binary packages built from the source packages which installed the libfaad2_drm.so and libfaac_drm.so files. I'm happy to work out how to modify the packaging scripts if you are happy for them to be added to Debian. cheers Julian jcable-guest on alioth.___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
