On Thu, 6 Aug 2015 08:34:41 +0900
Olaf Meeuwissen olaf.meeuwis...@avasys.jp wrote:
# Maybe after the release would be a good time to blow the dust of the
# SANE 2 draft document and see what parts can be safely added to SANE 1
# without breaking API or ABI but that's food for sane-standard.
Hello,
On Aug 5 08:21 Olaf Meeuwissen wrote (excerpt):
Johannes Meixner writes:
...
My re-add-SANE_CAP_ALWAYS_SETTABLE.patch re-adds SANE_CAP_ALWAYS_SETTABLE
to sane.h which was erroneously removed in sane-backends-1.0.20 so that
sane-frontends and xsane can no longer build, see
Hello,
On Aug 5 09:53 Olaf Meeuwissen wrote (excerpt):
m. allan noah writes:
I removed SANE_CAP_ALWAYS_SETTABLE because it was not in the sane
standard
...
Distributions don't get to decide the SANE standard ;-)
Of course not!
Distributions only try to keep things working when things
I understand your frustration. It was a difficult decision for me to
remove it. But frankly, it's meaning is undefined, and so any use of
this CAP in a frontend is questionable. What are they using it to
signify?
allan
On Wed, Aug 5, 2015 at 5:51 AM, Johannes Meixner jsm...@suse.de wrote:
Hello,
On Aug 5 07:47 m. allan noah wrote (excerpt):
What are they using it to signify?
I cannot answer this right now because I do not maintain
SANE frontends packages for openSUSE (see my other mail).
Right now I checked skanlite and there is
no SANE_CAP_ALWAYS_SETTABLE in its sources.
Just FYI: regarding xsane there is no usage of SANE_CAP_ALWAYS_SETTABLE in
0.998 any more. And there is a related entry in the changelog. Therefore xsane
should not cause issues as well.
HTH,
take care
Dieter Jurzitza
--
---
Hi Johannes,
Sorry if my reply hit a raw nerve. Didn't mean to.
I just wanted to point out that SANE_CAP_ALWAYS_SETTABLE is not part of
the specification and therefore your suggestion to add it to sane.h was
a bit misguided. You are of course free to keep that patch in the SUSE
packaging of
m. allan noah writes:
I removed SANE_CAP_ALWAYS_SETTABLE because it was not in the sane
standard, and the only backend that used it set it on every option. As
it's intended purpose was not defined by standard, I hoped that it
would disappear. If the distros are going to shove it back in, I
I removed SANE_CAP_ALWAYS_SETTABLE because it was not in the sane
standard, and the only backend that used it set it on every option. As
it's intended purpose was not defined by standard, I hoped that it
would disappear. If the distros are going to shove it back in, I guess
that will never happen.
Johannes Meixner writes:
Everey Linux distribution should submit their patches to SANE
upstream (provided their changes make sense for upstream).
Here our (i.e. openSUSE) patches that we still have:
[...]
2)
My re-add-SANE_CAP_ALWAYS_SETTABLE.patch re-adds SANE_CAP_ALWAYS_SETTABLE
to
10 matches
Mail list logo
