On Wed, 11 Sep 2002, Fernando Pablo Lopez-Lezcano wrote:
> > If the API change is desirable and _has_ to be made there
> > should be an announcement (to alsa-dev which is where I assume
> > is where all developers of alsa applications are subscribed
> > to), and the library version should be increased so that an
> > application compiled with the old version will not just
> > segfault when run under the new drivers...
>
> Correct me if I'm wrong but bumping the library version number
> from .so.2 to .so.3 with api changes would also enable orderly
> migration _if_ the interface between the library and the
> drivers does not change. I would be able to have both a .so.2
> and a .so.3 in the system, so that old, not yet converted
> programs would work fine and new programs using the .so.3
> library would also work. Eventually, when all programs are
> updated and recompiled to use .so.3, the .so.2 could be just
> erased and would be history. Am I dreaming?
Nope. I'll do that (it's already on my HDD), but I'll have to change more
snd_pcm_hw_params_* functions to unify the access and let recognize
the error code to applications.
Jaroslav
-----
Jaroslav Kysela <[EMAIL PROTECTED]>
Linux Kernel Sound Maintainer
ALSA Project http://www.alsa-project.org
SuSE Linux http://www.suse.com
-------------------------------------------------------
In remembrance
www.osdn.com/911/
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
