[sbopkg-users] sbopkg.conf

[Bradley D. Thornton]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Oh man!

I just looked myself. Yup. Sure enough, after the last update all of my
packages are going to /tmp instead of /usr/local/packages.

Now that I've realized this, I do recall wondering why sbopkg didn't ask
me if I wanted to take my custom config over the default in the SlackBuilds.

I would have expected, especially since I did the update via upgradepkg,
that I would have ended up with a .new file instead.

hm...

Okay, good to know :) ~/.sbopkg.conf it is then ;)

On 03/01/2011 08:33 PM, slakmagik wrote:
> On 2011-03-01 (Tue) 21:52:54 [-0600], Bill Kirkpatrick wrote:
>> Folks,
>> I just got around to updating my laptop to sbopkg-0.34.1 & realized that
>> every time I upgrade, I have to edit my sbopkg.conf file because I don't
>> keep my sources in the suggested location. I made the following change to
>> sbopkg.conf, so as not to have to worry about that in future, I hope.
>>
>> # $Id: sbopkg.conf.new 857 2011-02-05 03:19:19Z slakmagik $
>> #
>> # Please read the sbopkg.conf(5) man page for information about this
>> # configuration file, including an explanation of how to set these
>> # variables.
>>
>> *# Read personallized configuration file if it exists;
>> #  - usually called 'sbo.conf'.
>> # Changes may be made in the personalized file, not this one.
>> CONFFILE=${CONFFILE:-"/etc/sbopkg/sbo.conf"}
>> [ -f ${CONFFILE} ] && . ${CONFFILE}
>> *
>> # The following variables are used by sbopkg and by the SlackBuild
>> # scripts themselves.  They must be exported for this reason.
>> export TMP=${TMP:-/tmp/SBo}
>> export OUTPUT=${OUTPUT:-/tmp}
>>
>> My sbo.conf is:
>>
>> SRCDIR=/mnt/spock/sbopkg/src
>> QUEUEDIR=/mnt/spock/sbopkg/sbopkg-slackware-queues
>>
>> Any actual changes to sbopkg.conf would have to be dealt with on upgrade,
>> but then one hsould read that file thoroughly after an upgrade anyway.
>> Is this worth adding to the conf file?
> 
> You've discovered a major documentation bug. We've actually already had
> an implementation of a solution to this problem since 0.25.0 but, to my
> astonishment, this isn't documented anywhere but the NEWS file.
> 
> If you create a ~/.sbopkg.conf file, sbopkg will automatically source it
> after the system file, allowing you to override it.
> 
> Also, there's an -f flag (that *is* documented) as another way to
> specify it if you wanted to use an entirely different configuration.
> 
> If we didn't already have the mechanism in place, it would definitely be
> worth doing something about. :) Thanks for making me realize the
> documentation omission. I'll correct that soon.
> _______________________________________________
> sbopkg-users mailing list
> sbopkg-users at sbopkg.org
> http://sbopkg.org/mailman/listinfo/sbopkg-users

- -- 
Bradley D. Thornton
Manager Network Services
NorthTech Computer
TEL: +1.760.666.2703  (US)
TEL: +44.702.405.1909 (UK)
http://NorthTech.US

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Find this cert at x-hkp://pool.sks-keyservers.net

iQEcBAEBAwAGBQJNbeFUAAoJEE1wgkIhr9j3jbAH/Ryp1gmN/t/kx4SPXYmFgSzd
HDJcOKjA36j6RDTFQjM7nfEhLsxYe/eYSXQeqhUtkoFoHnJQCYgvLaFUTCfj14eQ
obURlXdBDqqev0aTvpo/orjUQYsd8eBaWFmuYKaWU+XQ/ZJX3fsaG8e+raFvtp2W
WdVevyWXIinm6BeXfHlPSEikUrdyy9vgA/4VCBGRtEnTPaff6qgLWzasqk2iKQCs
+aU7sNK9rd/7R6n8k3ld0XOu5aEBRWmEtFR0SWr6x22FNyYT/vMG9HsSMMGqZeAa
xdnCxa4Wrdy95sIhZLP27eaQXRp5Tq3sxxbXRpQFNhSRpaPcARzQKbDBqsWDCrs=
=WZCD
-----END PGP SIGNATURE-----