> > 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.
Great, thanks a lot. It'd be helpful if you could you post a small message to alsa-dev when you are done with that change in cvs. Then I can try to get a build that has the "backwards compatibility" old library and start migrating applications as they become "aware" of the new library. -- Fernando ------------------------------------------------------- In remembrance www.osdn.com/911/ _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
