Bug#269925: ITP: portaudio -- Portable audio I/O
Hi, Mikael Magnusson wrote: I choose to name them libportaudio0[-dev] and libportaudio19-0[-dev] with libportaudio0 and libportaudio19-0 as SONAMEs respectively, and I think my naming scheme has an advantages. If portaudio v19 when release is backward compatible with v18, then libportaudio19-0[-dev] can be renamed to libportaudio0[-dev]. I just did a diff between portaudio v18.1 and the CVS anspshot I packaged. They renamed functions (removing the old ones): e.g. PaQueryDevice - PaOSS_QueryDevice. And AFAIS function signatures, too. So v18 and v19 *are* ABI-incompatible (which also alreyd was implied of the API changes, see above). So you *need* to do a split completely and this means also wrt SONAMEs, v19 will not be compatible with pplications written for/linked against v18. According to the first paragraph in Debian Policy Manual section 10.2 Libraries, you must compile all source twice. Isn't this required anymore, as I can't see this happen in your package? Well... I never saw bad implications of static libraries built with -fPIC, contrary I saw that this is good since some applications/other dynamic libraries wanting to link against portaudio will not fail. Some arch require -fPIC for linking into a (dynamic) app and dynamic librar
Bug#269925: ITP: portaudio -- Portable audio I/O
Rene Engelhard wrote: Hi, [ since OOo 1.1.5 and 2.0 are able to use portaudio/sndfile I am interested in this package, too ] Mikael Magnusson wrote: I have uploaded an experimental version to mentors.debian.net: http://mentors.debian.net/debian/pool/main/p/portaudio/portaudio_18.1-0.dsc What is the status of this ITP? There was a problem with the license, and I don't know if it has been resolved. Sorry to say that but that package looks broken to me. Is upstreams or my package broken? As far as I can see in the source the portaudio upstreams have no clue about SONAMEs. Currently, when you link against libportaudio.so, you get a dependency on libportaudio.so which is bad. Either we just ship the static library (bad also) or we fix it by giving the packages a halfproper SONAME. Looking at the source further they apparently broke API/ABI without even caring about SONAME stuff. I saw you copnverted the stuff using libtool and apparently gave this stuff the SONAME libportaudio.so.0 (judging from the package name). As I said, since the portaudio upstreams don't seem to care about proper version numbering this is risky. So, to do the second method, I did libportaudio0.0.18[-dev] and libportaudio0.0.19[-dev] packages with the libportaudio0.0.x as SONAME so that this works at least. I choose to name them libportaudio0[-dev] and libportaudio19-0[-dev] with libportaudio0 and libportaudio19-0 as SONAMEs respectively, and I think my naming scheme has an advantages. If portaudio v19 when release is backward compatible with v18, then libportaudio19-0[-dev] can be renamed to libportaudio0[-dev]. I don't think this will be a nightmare judging the long release cycles - considering that 18.1 is years old and v19 not even released yet. Anyway, my current (source) packages are at http://people.debian.org/~rene/portaudio/. (I included the docs in -dev since it makes no sense to make a own package for that less kb...) According to the first paragraph in Debian Policy Manual section 10.2 Libraries, you must compile all source twice. Isn't this required anymore, as I can't see this happen in your package? Have you looked at my 20_unix_oss patch, which fixes bugs in Pa_StreamTime and Pa_UpdateStreamTime? I can upload them if wished. I also can add you as co-maintainer if you wish... Maybe. Grüße/Regards, René Regards, Mikael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#269925: ITP: portaudio -- Portable audio I/O
Hi, [ since OOo 1.1.5 and 2.0 are able to use portaudio/sndfile I am interested in this package, too ] Mikael Magnusson wrote: I have uploaded an experimental version to mentors.debian.net: http://mentors.debian.net/debian/pool/main/p/portaudio/portaudio_18.1-0.dsc What is the status of this ITP? Sorry to say that but that package looks broken to me. As far as I can see in the source the portaudio upstreams have no clue about SONAMEs. Currently, when you link against libportaudio.so, you get a dependency on libportaudio.so which is bad. Either we just ship the static library (bad also) or we fix it by giving the packages a halfproper SONAME. Looking at the source further they apparently broke API/ABI without even caring about SONAME stuff. I saw you copnverted the stuff using libtool and apparently gave this stuff the SONAME libportaudio.so.0 (judging from the package name). As I said, since the portaudio upstreams don't seem to care about proper version numbering this is risky. So, to do the second method, I did libportaudio0.0.18[-dev] and libportaudio0.0.19[-dev] packages with the libportaudio0.0.x as SONAME so that this works at least. I don't think this will be a nightmare judging the long release cycles - considering that 18.1 is years old and v19 not even released yet. Anyway, my current (source) packages are at http://people.debian.org/~rene/portaudio/. (I included the docs in -dev since it makes no sense to make a own package for that less kb...) I can upload them if wished. I also can add you as co-maintainer if you wish... Grüße/Regards, René -- .''`. René Engelhard -- Debian GNU/Linux Developer : :' : http://www.debian.org | http://people.debian.org/~rene/ `. `' [EMAIL PROTECTED] | GnuPG-Key ID: 248AEB73 `- Fingerprint: 41FA F208 28D4 7CA5 19BB 7AD9 F859 90B0 248A EB73 signature.asc Description: Digital signature
Bug#269925: ITP: portaudio -- Portable audio I/O
Junichi Uekawa wrote: I looked at this in the past, and I avoided doing this package; It has an additional licensing clause to a BSD license: Any person wishing to distribute modifications to the Software is requested to send the modifications to the original developer so that they can be incorporated into the canonical version. An I felt rather uneasy about that. A clarification from upstream author that this clause is not a binding one (that one does not have to send the changes) might be useful. regards, junichi Thanks for the information, but I don't think there should be a problem, because portaudio is already distributed in Debian main. Audacity uses portaudio and it's included in its source archive. Regards, Mikael
Bug#269925: ITP: portaudio -- Portable audio I/O
Hi, Just FYI * Package name: portaudio Version : 18.1 Upstream Author : Ross Bencina [EMAIL PROTECTED] Phil Burk [EMAIL PROTECTED] * URL or Web page : http://www.portaudio.com/ * License : Modified BSD style license I looked at this in the past, and I avoided doing this package; It has an additional licensing clause to a BSD license: Any person wishing to distribute modifications to the Software is requested to send the modifications to the original developer so that they can be incorporated into the canonical version. An I felt rather uneasy about that. A clarification from upstream author that this clause is not a binding one (that one does not have to send the changes) might be useful. regards, junichi
Bug#269925: ITP: portaudio -- Portable audio I/O
Package: wnpp Severity: wishlist * Package name: portaudio Version : 18.1 Upstream Author : Ross Bencina [EMAIL PROTECTED] Phil Burk [EMAIL PROTECTED] * URL or Web page : http://www.portaudio.com/ * License : Modified BSD style license Description : Portable audio I/O PortAudio is a portable audio I/O library designed for cross-platform support of audio. It uses a callback mechanism to request audio processing. Audio can be generated in various formats, including 32 bit floating point, and will be converted to the native format internally. I have uploaded an experimental version to mentors.debian.net: http://mentors.debian.net/debian/pool/main/p/portaudio/portaudio_18.1-0.dsc Regards, Mikael Magnusson
