> On Sun, 5 Apr 1998, [ISO-8859-1] Mikko Työläjärvi wrote:
>
> > Question 1:
> >
> > Is it necessary to keep all the loadable backends in the standard
> > library path? I'm getting an uneasy feeling when sane singlehandedly
> > doubles the number of entries in my /usr/local/lib, with something
> > that could be considered as internal to sane.
> >
> > Am I missing something, or could they be moved to (for example)
> > /usr/local/lib/sane/? Aren't the backends just dlopen()ed?
>
> Aren't you at liberty to use another path? Just add the proper parameter
> when runing ./configure should do the trick.
>
Of course I could do that. But still I think there is a difference
between libsane.so, which executables using sane are dynamically
linked with and the backends, that are internal to sane.
Then again, it's no big deal. If it really bothers me, I'll do
something about it.
/Mikko
Mikko Tyo"la"ja"rvi________________________________mikko@securitydynamics.com
SecurityDynamics
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com