[sane-devel] Patch to make XSane work with SANE 1.1
alesh.slovak at avasys.jp
Tue Oct 14 06:45:03 UTC 2008
> It is out of the picture to 'back out' other people work. This work has been
> discussed publicly months ago, and development happened in the open.
> If you want to keep with SANE 1.0, then use the SANE 1.0 branch that has been
> planned when work began on SANE 1.1. People interested can start using it,
> backporting the changes they want -provided the 1.0 standard is respected-.
> There is room enough for SANE 1.0 and next SANE version to coexist.
> I hope the scope of this discussion is to sort out if we call the next
> version SANE 1.1 or 2.0 with the according soname.
My understanding of the problem is that a SANE API incompatibility crept
in unnoticed, and now it is being decided whether SANE should go ahead
and be released as 2.0, which is incompatible with 1.0 or as intended, a
backwards compatible 1.1 with the incompatible features removed.
I am not suggesting to throw out anyones code, what I suggested was that
if you are going to make incompatible changes, there may be other
changes to consider for inclusion and more time should be spent on it.
Since you are going to be breaking the API you may as well try to get
other things that might break the API in there at the same time. If you
release a new backwards incompatible SANE 2.0, then we are going to have
to live with that API for at least a while.
I was under the impression that the next release would be a backwards
compatible release, SANE 1.1. Releasing a backwards incompatible SANE
2.0 all of a sudden seems to be jumping the gun a bit if you ask me.
Alesh Slovak Linux Team -- AVASYS Corporation
alesh.slovak at avasys.jp http://avasys.jp
More information about the sane-devel