sane-project-website/old-archive/1998-04/0069.html

124 wiersze
5.0 KiB
HTML

<!-- received="Sun Apr 5 17:22:50 1998 PDT" -->
<!-- sent="Sun, 5 Apr 1998 17:21:40 -0700" -->
<!-- name="Michael Polo" -->
<!-- email="mikep@Polo.NET" -->
<!-- subject="Re: sane 0.72pre meets FreeBSD [my system of package control]" -->
<!-- id="199804060021.RAA01796@enigma.Polo.NET" -->
<!-- inreplyto="sane 0.72pre meets FreeBSD [my system of package control]" -->
<title>sane-devel: Re: sane 0.72pre meets FreeBSD [my system of package control]</title>
<h1>Re: sane 0.72pre meets FreeBSD [my system of package control]</h1>
<b>Michael Polo</b> (<a href="mailto:mikep@Polo.NET"><i>mikep@Polo.NET</i></a>)<br>
<i>Sun, 5 Apr 1998 17:21:40 -0700</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#69">[ date ]</a><a href="index.html#69">[ thread ]</a><a href="subject.html#69">[ subject ]</a><a href="author.html#69">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0070.html">=?ISO-8859-1?Q?Mikko_Ty=F6l=E4j=E4rvi?=: "Re: sane 0.72pre meets FreeBSD"</a>
<li> <b>Previous message:</b> <a href="0068.html">Chris Pinkham: "Re: sane_read returning *len == 0"</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0071.html">becka@rz.uni-duesseldorf.de: "Re: sane 0.72pre meets FreeBSD [my system of package control]"</a>
<li> <b>Reply:</b> <a href="0071.html">becka@rz.uni-duesseldorf.de: "Re: sane 0.72pre meets FreeBSD [my system of package control]"</a>
<!-- reply="end" -->
</ul>
<!-- body="start" -->
<i>&gt; </i><br>
<i>&gt; On Sun, 5 Apr 1998, [ISO-8859-1] Mikko Työläjärvi wrote:</i><br>
<i>&gt; </i><br>
<i>&gt; &gt; Question 1:</i><br>
<i>&gt; &gt; </i><br>
<i>&gt; &gt; Is it necessary to keep all the loadable backends in the standard</i><br>
<i>&gt; &gt; library path? I'm getting an uneasy feeling when sane singlehandedly</i><br>
<i>&gt; &gt; doubles the number of entries in my /usr/local/lib, with something</i><br>
<i>&gt; &gt; that could be considered as internal to sane.</i><br>
<i>&gt; &gt; </i><br>
<i>&gt; &gt; Am I missing something, or could they be moved to (for example)</i><br>
<i>&gt; &gt; /usr/local/lib/sane/? Aren't the backends just dlopen()ed?</i><br>
<i>&gt; </i><br>
<i>&gt; Aren't you at liberty to use another path? Just add the proper parameter</i><br>
<i>&gt; when runing ./configure should do the trick.</i><br>
<i>&gt; </i><br>
<i>&gt; Hugo.</i><br>
<p>
<p>
I think having a /usr/local/lib/sane is a good idea. Perl, xemacs<br>
and gimp do this.<br>
<p>
I have 84 entries for sane out of 140 total, and every backend<br>
seems to have 5 entries!<br>
<p>
<p>
By the way, I tried using 'the proper parameter' for configure for a<br>
long time before I just gave up and put everything in /usr/local.<br>
I hate having to doctor up LD_LIBRARY_PATH (on solaris) before running<br>
an executable.<br>
<p>
<p>
<p>
My trick for keeping track of what installed and what's not installed<br>
is to make /usr/local owned by group 'build'. When I add a new<br>
package, I create a new user for that package.<br>
<p>
my script to create a user (on solaris anyway) is:<br>
<p>
useradd -d /export/home/build -g build -s /usr/local/bin/bash u_$1<br>
<p>
for sane, I created a user u_sane.<br>
<p>
I also did a 'chmod g+s /usr/local' a while back - when a new <br>
subdirectory anyway under /usr/local is created, the group is<br>
set to build.<br>
<p>
So any new package I get can be built and installed in /usr/local<br>
with 'make install'.<br>
<p>
Install a package:<br>
<p>
log in as root:<br>
# INSTALL_SETUP gcc<br>
<p>
(my one-line script above executes - user u_gcc is added with the<br>
next available user id and groupid build)<br>
<p>
# su - u_gcc<br>
u_gcc:~&gt; gtar xvfz gcc-2.7.2.3.tar.gz<br>
u_gcc:~&gt; cd gcc-2.7.2.3<br>
u_gcc:~/gcc-2.7.2.3&gt; ./configure ...blah blah...; make install<br>
<p>
<p>
Find out what was installed:<br>
<p>
find /usr/local -user u_gcc<br>
<p>
Remove a package:<br>
<p>
find /usr/local -user u_gcc | xargs rm<br>
<p>
sometimes you need a:<br>
<p>
find /usr/local -user u_gcc -depth | xargs rmdir<br>
<p>
And nothing can install in /etc, /var or /bin other such crap<br>
because there aren't permissions.<br>
<p>
Anyway, that's my system. Maybe it'll help someone.<br>
<p>
Mike<br>
<p>
<p>
<pre>
--
Source code, list archive, and docs: <a href="http://www.mostang.com/sane/">http://www.mostang.com/sane/</a>
To unsubscribe: echo unsubscribe sane-devel | mail <a href="mailto:majordomo@mostang.com">majordomo@mostang.com</a>
</pre>
<!-- body="end" -->
<p>
<ul>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0070.html">=?ISO-8859-1?Q?Mikko_Ty=F6l=E4j=E4rvi?=: "Re: sane 0.72pre meets FreeBSD"</a>
<li> <b>Previous message:</b> <a href="0068.html">Chris Pinkham: "Re: sane_read returning *len == 0"</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0071.html">becka@rz.uni-duesseldorf.de: "Re: sane 0.72pre meets FreeBSD [my system of package control]"</a>
<li> <b>Reply:</b> <a href="0071.html">becka@rz.uni-duesseldorf.de: "Re: sane 0.72pre meets FreeBSD [my system of package control]"</a>
<!-- reply="end" -->
</ul>