From bkirkp at gmail.com Wed Mar 2 03:52:54 2011 From: bkirkp at gmail.com (Bill Kirkpatrick) Date: Tue, 1 Mar 2011 21:52:54 -0600 Subject: [sbopkg-users] sbopkg.conf Message-ID: 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? Regards, Bill -------------- next part -------------- An HTML attachment was scrubbed... URL: From slakmagik at gmail.com Wed Mar 2 04:33:49 2011 From: slakmagik at gmail.com (slakmagik) Date: Tue, 1 Mar 2011 23:33:49 -0500 Subject: [sbopkg-users] sbopkg.conf In-Reply-To: References: Message-ID: <20110302043349.GA2589@devbox> 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. From Bradley at NorthTech.US Wed Mar 2 06:19:00 2011 From: Bradley at NorthTech.US (Bradley D. Thornton) Date: Tue, 01 Mar 2011 22:19:00 -0800 Subject: [sbopkg-users] sbopkg.conf In-Reply-To: <20110302043349.GA2589@devbox> References: <20110302043349.GA2589@devbox> Message-ID: <4D6DE154.4090803@NorthTech.US> -----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----- From bkirkp at gmail.com Wed Mar 2 19:03:25 2011 From: bkirkp at gmail.com (B Kirkpatrick) Date: Wed, 02 Mar 2011 13:03:25 -0600 Subject: [sbopkg-users] sbopkg.conf In-Reply-To: <20110302043349.GA2589@devbox> References: <20110302043349.GA2589@devbox> Message-ID: <4D6E947D.4060508@gmail.com> On 03/01/2011 10: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 > This actually points at a major brain fade of my own. I use the SBo-git/current repository & when I set it in sbopkg, it creates ~/.sbopkg.conf with REPO_NAME & REPO_BRANCH in it. I just never thought to put anything else in there! Thanks a lot for a very good piece of software. Bill From slakmagik at gmail.com Wed Mar 2 23:47:35 2011 From: slakmagik at gmail.com (slakmagik) Date: Wed, 2 Mar 2011 18:47:35 -0500 Subject: [sbopkg-users] sbopkg.conf In-Reply-To: <4D6DE154.4090803@NorthTech.US> References: <20110302043349.GA2589@devbox> <4D6DE154.4090803@NorthTech.US> Message-ID: <20110302234735.GA15146@devbox> On 2011-03-01 (Tue) 22:19:00 [-0800], Bradley D. Thornton wrote: > -----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. > Well, if you don't have a .new file, I'm not sure what happened. You should, and it and the doinst.sh are in the 0.34.1 package. If you don't and it's anything sbopkg is doing wrong, please report back. From slakmagik at gmail.com Wed Mar 2 23:51:32 2011 From: slakmagik at gmail.com (slakmagik) Date: Wed, 2 Mar 2011 18:51:32 -0500 Subject: [sbopkg-users] sbopkg.conf In-Reply-To: <4D6E947D.4060508@gmail.com> References: <20110302043349.GA2589@devbox> <4D6E947D.4060508@gmail.com> Message-ID: <20110302235132.GB15146@devbox> On 2011-03-02 (Wed) 13:03:25 [-0600], B Kirkpatrick wrote: > This actually points at a major brain fade of my own. I use the > SBo-git/current repository & when I set it in sbopkg, it creates > ~/.sbopkg.conf with REPO_NAME & REPO_BRANCH in it. I just never thought > to put anything else in there! Thanks a lot for a very good piece of > software. > Bill > On behalf of Chess and Mauro and myself, you're welcome. :) This should be better: http://code.google.com/p/sbopkg/source/detail?r=864 From slakmagik at gmail.com Thu Mar 10 05:04:12 2011 From: slakmagik at gmail.com (slakmagik) Date: Thu, 10 Mar 2011 00:04:12 -0500 Subject: [sbopkg-users] sbopkg 0.35.0 pseudo-rc1 Message-ID: <20110310050412.GA5970@devbox> Hello folks. We're not going to do an actual release candidate for this but if you'd like to try it out, you can download http://sbopkg.googlecode.com/svn/trunk/tools/sspm and run it (in a vm, ideally). You should get a shiny new almost-0.35.0 for testing. Note that there are several file renames and that name collisions in /etc/repos.d, while highly unlikely, are possible, resulting in clobbered files if they aren't moved. Also any custom renames files in /etc/sbopkg/renames.d need to have '.renames' appended to them in order to be recognized. It would be good to get that bash completion into this release but that shouldn't affect sbopkg itself. So, other than that and bugfixes, there hopefully won't be any more changes. Whenever Slackware goes out, if sbopkg seems to be bug-free, we'll amble along awhile after. :) For those about to test, we salute you! From rw at rlworkman.net Thu Mar 10 05:26:05 2011 From: rw at rlworkman.net (Robby Workman) Date: Wed, 9 Mar 2011 23:26:05 -0600 Subject: [sbopkg-users] sbopkg 0.35.0 pseudo-rc1 In-Reply-To: <20110310050412.GA5970@devbox> References: <20110310050412.GA5970@devbox> Message-ID: <20110309232605.104638fb@liberty.rlwhome.lan> On Thu, 10 Mar 2011 00:04:12 -0500 slakmagik wrote: > For those about to test, we salute you! ++ :-) -RW From slakmagik at gmail.com Thu Mar 10 19:33:32 2011 From: slakmagik at gmail.com (slakmagik) Date: Thu, 10 Mar 2011 14:33:32 -0500 Subject: [sbopkg-users] bash completion In-Reply-To: <201102031830.55398.sftp.mtuci@gmail.com> References: <201101080251.27851.sftp.mtuci@gmail.com> <201101090322.06214.sftp.mtuci@gmail.com> <20110109024642.GA30920@devbox> <201102031830.55398.sftp.mtuci@gmail.com> Message-ID: <20110310193332.GA22387@devbox> Thanks for this - and sorry for taking so long to get back to you. On 2011-02-03 (Thu) 18:30:54 [+0300], Sergey V. wrote: > > TODO: completion not work for syntax like this > sbopkg -i|-b "pkg1 pkg2" > (now I do not see any other issues) > Yeah, completion on quoted args would good. I haven't looked into or experimented with programmable completion much, so here are just some vague notes and questions: > Please review or/and test it. > # bash completion for sbopkg tool > > _sbopkg() > { > COMPREPLY=() > > local cur="${COMP_WORDS[COMP_CWORD]}" > local prev="${COMP_WORDS[COMP_CWORD-1]}" (Not important, but maybe:) + local opts=$(echo "-{b,c,d,e,f,g,h,i,k,l,o,P,p,q,R,r,s,u,V,v}") > > if [[ "$cur" == -* ]]; then - COMPREPLY=( $( compgen -W '-b -c -d -e -f -g -h -i -k -l \ - -o -P -p -q -R -r -s -u -V -v' -- "$cur" ) ) + COMPREPLY=( $( compgen -W "$opts" -- "$cur" ) ) > return 0 > fi > > case $prev in > -e) > COMPREPLY=( $( compgen -W 'ask continue stop' -- "$cur" ) ) > return 0 > ;; > -f) > COMPREPLY=( $( compgen -f -- "$cur" ) ) > return 0 > ;; > -d) > COMPREPLY=( $( compgen -d -- "$cur" ) ) > return 0 > ;; > -V) > COMPREPLY=( $( compgen -W "? \ > $(sbopkg -V ? 2>&1 | cut -s -f1)" -- "$cur" ) ) > return 0 > ;; - -i|-b) + -b|-g|-i|-s) (The -g is pretty useless but consistent and doesn't seem to hurt anything. The -s won't help if the search string is the end of the desired string, but will if it's the beginning.) > ;; > *) > return 0 > ;; > esac > > local config="/etc/sbopkg/sbopkg.conf" > > for (( i=${#COMP_WORDS[@]}-1; i>0; i-- )); do > if [[ "${COMP_WORDS[i]}" == -f ]]; then > config="${COMP_WORDS[i+1]}" > break > fi > done > > if [ ! -r "$config" ]; then > return 0 > fi > > . $config > > for (( i=1; i<${#COMP_WORDS[@]}; i++ )); do > case "${COMP_WORDS[i]}" in > -V) > REPO_NAME="${COMP_WORDS[i+1]%%/*}" > REPO_BRANCH="${COMP_WORDS[i+1]#*/}" > ;; > -d) > REPO_ROOT="${COMP_WORDS[i+1]}" > ;; > esac > done > > if [ ! -r "$REPO_ROOT/$REPO_NAME/$REPO_BRANCH/SLACKBUILDS.TXT" ]; then > return 0 > fi > COMPREPLY=( $( sed -ne "/^SLACKBUILD NAME: $cur/{s/^SLACKBUILD NAME: //;p}"\ > $REPO_ROOT/$REPO_NAME/$REPO_BRANCH/SLACKBUILDS.TXT ) > $( cd $QUEUEDIR; compgen -f -X "!*.sqf" -- "$cur" ) ) > } && complete -o filenames -F _sbopkg sbopkg The only real issue I see is that the output of tab completion on -V isn't entirely correct. It currently produces ? master 11.0 12.0 12.1 12.2 13.0 13.1 local and if you accidentally tab complete on 'sbopkg -V ?' it converts it to sbopkg -V \? (which doesn't hurt, but doesn't look great.) It would be better to produce ? SBo/11.0 SBo/12.1 SBo/13.0 local/local SB64/master SBo/12.0 SBo/12.2 SBo/13.1 Changing the last line's 'filenames' to 'default' does this, but this results in unwanted side effects such as trying to complete things that have no completions with what's in the current directory. Anyway, I can certainly add this as is, but changing the -V output would be good - it's not an issue now but, if multiple repos had a 'master', then 'master master master 11.0' wouldn't be ideal output. :) Thanks again.