Re: Providing a non-free alternative to a free package
firstname.lastname@example.org (Olе Streicher) writes:
> Björn Esser <email@example.com> writes:
>> So I'd suggest name the free one slalib and the other one
>> slalib-nonfree or vice versa (like the unrar example).
> The problem is that I want the dependent programs to be linked against
> any of them.
> For example "saods9" would use slalib as a shared library, and I want to
> git the user a choide to run it either with the free, or with the
> non-free version.
Are the two libraries actually ABI compatible? Somehow I doubt that, but
I might just be too sceptic when it comes to non-free software.