[sane-devel] SANE_CAP_ALWAYS_SETTABLE (was Re: Preparing for a sane-backends release)
m. allan noah
kitno455 at gmail.com
Wed Aug 5 11:47:47 UTC 2015
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
On Wed, Aug 5, 2015 at 5:51 AM, Johannes Meixner <jsmeix at suse.de> wrote:
> 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
>> Distributions don't get to decide the SANE standard ;-)
> Of course not!
> Distributions only try to keep things working when things break
> between various upstream projects (see my other mail).
>> If any frontends still use it, it is those frontends that need fixing.
> In theory yes.
> I practice it is me who is blamed when sane-backends "break" other
> frontends and then I must "fix" sane-backends (see my other mail).
> Only for the fun:
> It is the same when other programs use undocumented private API
> calls from CUPS (e.g. by blind copy and paste CUPS source code).
> When later the other programs break because CUPS' private API
> changed, then they cry "CUPS is to blame: CUPS is broken" ;-)
> Kind Regards
> Johannes Meixner
> SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard,
> Dilip Upmanyu, Graham Norton - HRB 21284 (AG Nuernberg)
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> Unsubscribe: Send mail with subject "unsubscribe your_password"
> to sane-devel-request at lists.alioth.debian.org
"well, I stand up next to a mountain- and I chop it down with the edge
of my hand"
More information about the sane-devel