mirrors/sbopkg
2
0
Fork 0
mirror of https://github.com/sbopkg/sbopkg synced 2024-11-09 19:50:25 +03:00
Code Issues Packages Projects Releases Wiki Activity

Documentation changes to reflect the new(est) ARCH issues.

Browse Source 
Add the possible ARCH-discrepancy issue to KNOWN_ISSUES and change
sbopkg.conf(5) to reflect how we currently process ARCH.
This commit is contained in:
slakmagik 2010-05-26 03:08:53 +00:00
parent 42300db6db
commit e445401c90
2 changed files with 19 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
src/usr/doc/KNOWN_ISSUES
View File

@ -18,7 +18,7 @@ tools it uses:
Workaround: use dialog's own exit methods - its buttons, escape, ^C, etc.
* when checking for updates, for some packages Sbopkg may tell you
* when checking for updates, for some packages sbopkg may tell you
"Note: repo version not obtainable by standard method, may be inaccurate.".
This happens with packages whose version is very difficult/impossible to
determine without actually building the package -- one example of this at
@ -44,3 +44,10 @@ tools it uses:
not be able to download these sources.
Workaround: add --no-check-certificate to WGETFLAGS in sbopkg.conf
* certain packages build kernel modules and need to (re)set the ARCH to 'x86'
on i?86 (32-bit) systems which may result in packages with 'x86' as the ARCH
in the file name, while sbopkg will display the specific ARCH of your system
(or the ARCH you've set) in certain cases, such as in widget titles.
Workaround: none needed

21
src/usr/man/man5/sbopkg.conf.5
View File

@ -273,19 +273,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
.SH ABOUT THE ARCH VARIABLE
You may be wondering why ARCH is not a configuration setting in the
default sbopkg.conf file. The reason is that it does not have to be. If ARCH
is not set, sbopkg does some checking (using 'uname -m') to determine what the
system's architecture is. If the architecture is x86, x86_64, or arm*, then
sbopkg automatically sets ARCH to i486, x86_64, or arm, respectively. If ARCH
is set, sbopkg will inherit that setting. 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.
Finally, if ARCH is not set by the user and sbopkg does not detect one of the
previously mentioned architectures, then ARCH will be set by whatever is in
the SlackBuild scripts. Note that the SlackBuild may, in certain instances,
discard or override previous ARCH settings if this is required for the build.
.SH FILES
.B /etc/sbopkg/sbopkg.conf