packaging jack - details on "plan B"

[Jonas Smedegaard]

On Fri, Apr 23, 2010 at 02:32:45PM -0500, Gabriel M. Beddingfield wrote:

>Therefore, any old program will work without recompile on a new 
>libjack0.  Jack 2 (formerly jackdmp) has also rigorously maintained 
>binary compatability with Jack 1.[3]

[...]

>[3] Going backwards has never been promised, though.  A
>    program compiled against 0.118.0 will work with 0.34.0.
>    However, the use of weak symbols for new features may
>    make this available.

Isn't it exactly "going backwards" if jackd2 becomes the default and 
jackd1 only an optional alternative?  Then applications are compiled 
against jackd2 and potentially using jackd1 at runtime.  Is that assured 
to work too, or only hopefully working if weak symbols work out as 
planned?


Kind regards,

  - Jonas

-- 
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

  [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20100423/303401a3/attachment.pgp>