add info about ARCH to sbopkg.conf(5) man page

This commit is contained in:
chess.griffin 2009-09-07 02:36:09 +00:00
parent 9c16496ef3
commit 8dbba9f417

View file

@ -10,7 +10,8 @@ The sbopkg.conf file contains configuration settings for
(8), a tool for interacting with the SlackBuilds.org ("SBo") (8), a tool for interacting with the SlackBuilds.org ("SBo")
repository, a collection of third-party SlackBuild scripts to build repository, a collection of third-party SlackBuild scripts to build
Slackware packages. A sample file is provided at Slackware packages. A sample file is provided at
/etc/sbopkg/sbopkg.conf.new. /etc/sbopkg/sbopkg.conf.new. Also, please see a note below about
$ARCH.
The different configuration options are: The different configuration options are:
@ -224,6 +225,20 @@ is ignored.
You can also export variables in sbopkg.conf that are not used by You can also export variables in sbopkg.conf that are not used by
sbopkg at all. sbopkg at all.
.SH ABOUT $ARCH
You may be wondering why $ARCH is not a configuration setting in the
sbopkg.conf file. The reason is that it does not have to be. First, sbopkg
does some checking (using 'uname -m') to determine what the system's
architecture is. If the architecture is x86_64, then sbopkg automatically
sets ARCH=x86_64. If the architecture is not x86_64, then sbopkg will inherit
any $ARCH settings in the environment. This means, the user can add, for
example, 'export ARCH=i686' in their .bashrc or similar file, or the user can
also execute something in the root terminal like 'export ARCH=i686 && sbopkg'.
The user can also manually add it to their sbopkg.conf file if they wish.
Finally, if $ARCH is not set by the user and sbopkg does not detect an x86_64
system, then $ARCH will default to whatever $ARCH is set to in the SlackBuild
scripts.
.SH FILES .SH FILES
.B /etc/sbopkg/sbopkg.conf .B /etc/sbopkg/sbopkg.conf
\ - File to specify configuration options. \ - File to specify configuration options.