Julien BLACHE jb at jblache.org writes:
Olaf Meeuwissen olaf.meeuwissen at avasys.jp wrote:
Hi,
Not doing so will make for a lot of big commits.
And? What's the point? As long as the build system updates are
self-contained and not mixed with other changes in the tree, we
couldn't care
Yes this works fine, thanks for the hint!
So in the end the solution for me was to change the xsane icon on the
desktop to include that extra parameter, and now can scan fine. Luckily
I have only three workstations total!
Regards,
Wouter van Marle
On Wed, 2009-01-07 at 13:30 -0600, gobo wrote:
On Tuesday 20 January 2009, Olaf Meeuwissen wrote:
autofoo one has to know. As for the amount of pain involved, I can
only think of the time it takes. Julien mentions versioning issues
and broken deployment but I have little experience with that.
You obviously never had to work with
On Tuesday 20 January 2009 02:41:14 m. allan noah wrote:
Date: Tuesday, January 20, 2009 @ 01:41:14
Author: kitno-guest
Path: /cvsroot/sane/sane-backends
Modified: ChangeLog doc/descriptions-external/brother2.desc
include/sane/sanei_thread.h sanei/sanei_thread.c
add
Olaf Meeuwissen olaf.meeuwissen at avasys.jp wrote:
Hi,
Acknowledged. It may even be a better approach as several Linux
distributions have a habit of running autoreconf --force before that
build (and for a good reason). Putting the hack in configure makes
at least sure they pick up on it.
oh, a mistake. I will back them out now... Sorry.
allan
On Tue, Jan 20, 2009 at 3:19 AM, Gerhard Jaeger gerhard at gjaeger.de wrote:
On Tuesday 20 January 2009 02:41:14 m. allan noah wrote:
Date: Tuesday, January 20, 2009 @ 01:41:14
Author: kitno-guest
Path:
Julien BLACHE wrote:
autofoo one has to know. As for the amount of pain involved, I can
only think of the time it takes. Julien mentions versioning issues
and broken deployment but I have little experience with that.
You obviously never had to work with broken libtool versions, which
Chris Bagwell chris at cnpbagwell.com wrote:
Hi,
So I think its safe to say that you've had some sort of bad experience
with some part of the autofoo chain in the past and have settle on
Not inside SANE. The most painful experience we've had here was
switching to modern autofoo versions
