[SCM] Free Firewire Audio Drivers (ffado.org) packaging branch, master, updated. upstream/2.0rc1+svn1539-21-g54ef3a4

[Felipe Sateler]

I accidentally replied to Adrian privately, moving back to the list. (BTW, 
Adrian, please don't CC me, I read the list :).

El martes 19 de mayo, Adrian Knoth escribió:
> On Tue, May 19, 2009 at 05:42:59PM +1000, Felipe Sateler wrote:
> > That part is OK. What I'm asking about is why does libffado1 Replaces:
> > libffado0.
> > Replaces means that files in the package overwrite files in the replaced
> > package.
>
> Ah. It's all about
>
>    /usr/share/libffado/configuration
>
> That's the driver configuration file which defines all the internal
> settings for the different devices. It is tightly coupled to the
> library, and it is version-specific. With a new release of libffado, the
> content of this file might be completely different. (happened four weeks
> ago, upstream introduced new config values to the file)
>
> So chapter 8.2 is talking about runtime support programs, and an
> extracted -runtime-package must not specify a soversion. This won't work
> in this case, because the library explicitly needs this version-specific
> configuration file.

There are solutions. For example, upstream could look for /u/s/l/configuration-
SOVERSION, or /u/s/libffado1/configuration. Another option would be to split 
that file into libffado-devices and make libffado1 Depends: libffado-devices (= 
${binary:Version})). But that would defeat the purpose of the policy rule.

>
> Would it help to add a "Conflicts" line, so only libffado0 or libffado1
> can be installed at the same time? This was my intention: get rid of
> libffado0, it's the old rc1, and everybody should use rc2.
>
> It doesn't make sense to use the older version, especially because
> libffado isn't used directly, but as a jackd backend - so jack will
> depend on libffado, and all the ffado-* packages must match exactly this
> version.

The aim of this policy is precisely to allow for both libraries to be present 
at once. As such, the optimal solution would be to version the configuration 
file, and distribute it with the package. I did that with csound, plugins are 
installed in a versioned directory, because they are coupled to the library 
version.


Saludos,
Felipe Sateler
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20090519/89769d04/attachment.pgp>