Ignore:
Timestamp:
09/01/2019 10:24:56 AM (5 years ago)
Author:
Pierre Labastie <pieere@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 9.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
Children:
cdb3add2
Parents:
9d0c26ed
Message:

sane-backends: the user running configure really need to belong to the scanner
group. Reintroduce the note about that, and use "sg" for configure

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@22078 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:
1 edited

Legend:

Unmodified
Added
Removed
  • pst/scanning/sane.xml

    r9d0c26ed r46c5976  
    154154<screen role="root"><userinput>groupadd -g 70 scanner</userinput></screen>
    155155
    156 <!-- The following seems to be obsolete: I've built sane several times
    157      as user pierre without adding it to the scanner group
    158156      <note>
    159157        <para>
    160           The user building <application>SANE</application>-backends should be
    161           a member of the <systemitem class="groupname">scanner</systemitem>
    162           group before proceeding. After you have added the user building the
    163           package to the <systemitem class="groupname">scanner</systemitem>
    164           group, issue the following command to create a new shell:
     158          <command>configure</command> assumes that the user building
     159          <application>SANE</application>-backends is a member of the
     160          <systemitem class="groupname">scanner</systemitem> group for testing
     161          the existence of this group. So the user building the package should
     162          be added to the <systemitem class="groupname">scanner</systemitem>
     163          group. As the <systemitem class="username">root</systemitem> user:
    165164        </para>
    166165
    167 <screen><userinput>su $(whoami)</userinput></screen>
    168 
    169         <para>
    170           Check the output of the <userinput>groups</userinput> command and
    171           ensure the user is a member of the
    172           <systemitem class="groupname">scanner</systemitem> group.
    173         </para>
     166<screen role="root"><userinput>usermod -G scanner -a <replaceable>username</replaceable></userinput></screen>
    174167      </note>
    175 -->
     168
    176169      <para>For a USB scanner, if you are linking to <xref linkend="libusb"/>,
    177170      include the configure switch --enable-libusb_1_0. Install
     
    179172      commands:</para>
    180173
    181 <screen><userinput>./configure --prefix=/usr        \
     174<screen><userinput>sg scanner -c "                  \
     175./configure --prefix=/usr        \
    182176            --sysconfdir=/etc    \
    183177            --localstatedir=/var \
    184178            --with-group=scanner \
    185             --with-docdir=/usr/share/doc/sane-backends-&sane-version; &amp;&amp;
     179            --with-docdir=/usr/share/doc/sane-backends-&sane-version;" &amp;&amp;
    186180make</userinput></screen>
    187181
     
    252246  <sect2 role="commands">
    253247    <title>Command Explanations</title>
     248
     249    <para>
     250      <command>sg scanner -c "..."</command>: runs the command between double
     251      quotes with principal group <systemitem
     252      class="groupname">scanner</systemitem>. This may be needed if the user
     253      has been newly added to group scanner, and has not looged out and in.
     254    </para>
    254255
    255256    <para><parameter>--sysconfdir=/etc</parameter>: This switch installs the
Note: See TracChangeset for help on using the changeset viewer.