Re: Sane config thoughts

John Stoffel (john.stoffel@ascend.com)
Thu, 22 Apr 1999 11:04:56 -0400 (EDT)

>> Hi guys,
>>
>> One of the things I really like about sane is that it works, and works
>> pretty well. The thing I really dislike is that when I compile the
>> code I build backends for scanners I've never even seen, much less
>> have on my computer.
>>
>> Would it make sense to implement some sort of configure time questions
>> to ask which backends you want compiled into our kernel?

Oliver> the backends are not compiled into your kernel. sane only
Oliver> build libraries that are installed on your harddisk.

Correct, I mis-typed here, and didn't proof read enough before
sending.

Oliver> The libraries are installed in /usr(/local)/lib/sane
Oliver> and all you have to pay is about 7 MB harddiskspace.

It's not so much the disk space, but the feeling that we shouldn't
bother to build backends that the user doesn't even have. And as much
as we think it true, disk space isn't infinite.

Oliver> If that is too much, feel free to remove the backend-libraries
Oliver> you don`t need

That's what I currently do now, but I was wondering if others felt the
same way and if I should bother to make a patch for this behavior.

John

--
Source code, list archive, and docs: http://www.mostang.com/sane/
To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com