With the release of 1.2rc2, Speex was split into two tarballs: speex and speexdsp: http://www.speex.org/downloads/ It would seem best to have the speex package continue to use the speex tarball, and to add a new package for speexdsp. There is an unfortunate circular dependency between the two packages: * speex optionally depends on speexdsp * speexdsp requires the headers from speex-devel to build (but does not link to libspeex) It seems like the easiest way to avoid problems while bootstrapping is to provide a build conditional.
Created attachment 966958 [details] proposed patch This should only be pushed once a speexdsp package is reviewed and ready to build.
I filed a review request for speexdsp as bug 1172829.
I don't know, is having two separate packages worth the extra bootstrapping step? They have the same upstream source and possibly will be released together, why not keep them in the same package and just create a new subpackage?
I think that the extra bootstrapping step is fine, as combining the two tarballs into a single package seems like it would bring additional problems, such is if there was ever a non-simultaneous release (which I suppose would lead to some awkwardness with mismatched version numbers). I also think that the legibility of a combined spec file would be worse, with having to configure and build twice, making sure to inject the include path for the speex headers into speexdsp, and so on. I would like to avoid handling speex linking to the uninstalled speexdsp, as well. Either way, splitting the libraries between two (sub-)packages will probably be the most disruptive change.
The review of the separate speexdsp package was approved in bug 1172829. If you prefer to go with the split package route, rather than the subpackage route, I can file the SCM request and coordinate the builds (I have speex commit access via the gnome-sig group). If you would prefer to go the subpackage route, I can come with an alternative patch for the speex package.
It's ok, commit the patch for the split. Thanks.
Split speexdsp and speex packages pushed and built for Rawhide. I have not made and changes to F21 or below, and I think it is probably best to leave those branches at rc1 (before the split) to avoid any problems it might cause, or at least delay any bumps until problems are shaken out in Rawhide.
Great, thanks!