From 8dbba9f4175fe3bd45b00e2c300111a6f8f803a9 Mon Sep 17 00:00:00 2001 From: "chess.griffin" Date: Mon, 7 Sep 2009 02:36:09 +0000 Subject: [PATCH] add info about ARCH to sbopkg.conf(5) man page --- src/usr/man/man5/sbopkg.conf.5 | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/src/usr/man/man5/sbopkg.conf.5 b/src/usr/man/man5/sbopkg.conf.5 index 14f6d96..95f8c21 100644 --- a/src/usr/man/man5/sbopkg.conf.5 +++ b/src/usr/man/man5/sbopkg.conf.5 @@ -10,7 +10,8 @@ The sbopkg.conf file contains configuration settings for (8), a tool for interacting with the SlackBuilds.org ("SBo") repository, a collection of third-party SlackBuild scripts to build 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: @@ -224,6 +225,20 @@ is ignored. You can also export variables in sbopkg.conf that are not used by 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 .B /etc/sbopkg/sbopkg.conf \ - File to specify configuration options.