From chess at chessgriffin.com Sun Dec 8 06:00:22 2013 From: chess at chessgriffin.com (Chess Griffin) Date: Sun, 08 Dec 2013 01:00:22 -0500 Subject: [sbopkg-users] Status of next sbopkg release Message-ID: <0baafcec4b14e3ad13c0268f4360fa88@eumx.net> Howdy folks- I thought I'd email the list to let folks know about the status of the next sbopkg release. As some of you may recall, I 'retired' from sbopkg development a few years ago and since that time the project had been taken up by my original sbopkg co-developers slakmagik and Maurio Giachero. I believe Mauro stopped using Slackware some time back but slakmagik has still been around and posted to this list as recently as this past July. He's done a fantastic job keeping sbopkg updated and making releases alongside new Slackware versions. Thank you, Slakmagik! I've emailed him a couple of times over the last 3-4 months about a new sbopkg release but have not gotten a reply. I'm hoping he'll see this post to the list and respond. As it stands now, the current sbopkg package available on the sbopkg.org website (and on the Google Code site) won't work with 14.1 without some minor modifications to the configuration files (see below for how to get the current sbopkg package working with 14.1). The source needs to be updated and a few minor issues posted in the Google Code issue tracker need to be addressed. So, here are options I'm thinking about (input welcome): 1. Staying with the current hosting and release system: I don't know if I still have access to the cardinal server (where sbopkg.org is hosted) to update the website when a new package is ready. I'll also need to figure out (or recreate) our release process. We had scripted some things to update the ChangeLog and make the man pages and package it all up in a Slackware package and source tarball. All of this will take some time. December is my super-busy time at work plus we have the holidays and all that. 2. Updating the Google Code svn with the 14.1 changes but not make a package: This would be trivial. I have write access to the SVN repo so I can update sbopkg in the source tree so it works with 14.1 and just not worry about the updated package. Let folks pull from SVN in other words. I'll probably do this no matter what since it's easy to do. 3. Moving the Google Code svn repo over to Github: Similar to #2. I've slowly gotten accustomed to Git (way behind most of you, I'm sure) and perhaps it make sense to consolidate it there. Part of me thinks that since sbopkg is just a shell script and some configuration files, we don't necessarily need a Slackware package ready to go, although I'm sure that it's easier for new users to install a package than pull from a git repo. Still, it's fairly easy to tag a release on github and just let folks grab the tarball and manually put stuff in the right place. If I did this, someone could also submit a SlackBuild to SBo to build a package from a tagged release. Github also makes it easy to host a webpage for sbopkg (which Willy and I do for the MSB project) and since I own the domain, I could point sbopkg.org to the github webpage. As far as the future goes, unfortunately, I just don't have time to actively maintain and develop sbopkg. I'm happy to keep it in the Google Code SVN repo or host it in a Github repo but in the event future bugfixes etc. are necessary, I won't be able to focus on them quickly and timely. Perhaps someone could offer to step up and take over maintenance and development. Perhaps folks have moved on to other tools and sbopkg is not needed anymore. Anyway, the point being that it would be good to hear from folks on their thoughts on sbopkg, whether they still use it, whether they stopped using it for something else, etc. Perhaps this input will spur someone to offer to help take over maintenance and development. I will note that according to the Google Code download page, the 0.36.0 package has been downloaded over 15,000 times. In the meantime, here is how to get the current sbopkg package (0.36.0) available on sbopkg.org working with Slackware 14.1: First, copy and paste the 14.0 line in /etc/sbopkg/repos.d/40-sbo.repo and make it 14.1 like so: # DO NOT EDIT THIS FILE. CHANGES WILL BE OVERWRITTEN. See the README. # Repo Branch Description Tag Tool Link CheckGPG SBo 14.1 "SBo repository for Slackware 14.1" _SBo rsync slackbuilds.org::slackbuilds/14.1 GPG SBo 14.0 "SBo repository for Slackware 14.0" _SBo rsync slackbuilds.org::slackbuilds/14.0 GPG SBo 13.37 "SBo repository for Slackware 13.37" _SBo rsync slackbuilds.org::slackbuilds/13.37 GPG SBo 13.1 "SBo repository for Slackware 13.1" _SBo rsync slackbuilds.org::slackbuilds/13.1 GPG SBo 13.0 "SBo repository for Slackware 13.0" _SBo rsync slackbuilds.org::slackbuilds/13.0 GPG SBo 12.2 "SBo repository for Slackware 12.2" _SBo rsync slackbuilds.org::slackbuilds/12.2 GPG SBo 12.1 "SBo repository for Slackware 12.1" _SBo rsync slackbuilds.org::slackbuilds/12.1 GPG SBo 12.0 "SBo repository for Slackware 12.0" _SBo rsync slackbuilds.org::slackbuilds/12.0 GPG SBo 11.0 "SBo repository for Slackware 11.0" _SBo rsync slackbuilds.org::slackbuilds/11.0 GPG Second, edit /etc/sbopkg/sbopkg.conf and change REPO_BRANCH in line 34 to 14.1: REPO_BRANCH=${REPO_BRANCH:-14.1} That's it! I hope everyone is having a great end of year. Thanks! -- Chess Griffin From rworkman at slackbuilds.org Sun Dec 8 19:16:08 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 8 Dec 2013 13:16:08 -0600 Subject: [sbopkg-users] Status of next sbopkg release In-Reply-To: <0baafcec4b14e3ad13c0268f4360fa88@eumx.net> References: <0baafcec4b14e3ad13c0268f4360fa88@eumx.net> Message-ID: <20131208131608.7f577455@home.rlworkman.net> You still have shell access, although the server name is now harrier.slackbuilds.org, and I'll mail privately with details. -RW On Sun, 08 Dec 2013 01:00:22 -0500 Chess Griffin wrote: > Howdy folks- > > I thought I'd email the list to let folks know about the status of > the next sbopkg release. > > As some of you may recall, I 'retired' from sbopkg development a few > years ago and since that time the project had been taken up by my > original sbopkg co-developers slakmagik and Maurio Giachero. I > believe Mauro stopped using Slackware some time back but slakmagik > has still been around and posted to this list as recently as this > past July. He's done a fantastic job keeping sbopkg updated and > making releases alongside new Slackware versions. Thank you, > Slakmagik! I've emailed him a couple of times over the last 3-4 > months about a new sbopkg release but have not gotten a reply. I'm > hoping he'll see this post to the list and respond. > > As it stands now, the current sbopkg package available on the > sbopkg.org website (and on the Google Code site) won't work with 14.1 > without some minor modifications to the configuration files (see > below for how to get the current sbopkg package working with 14.1). > The source needs to be updated and a few minor issues posted in the > Google Code issue tracker need to be addressed. > > So, here are options I'm thinking about (input welcome): > > 1. Staying with the current hosting and release system: I don't > know if I still have access to the cardinal server (where sbopkg.org > is hosted) to update the website when a new package is ready. I'll > also need to figure out (or recreate) our release process. We had > scripted some things to update the ChangeLog and make the man pages > and package it all up in a Slackware package and source tarball. All > of this will take some time. December is my super-busy time at work > plus we have the holidays and all that. > > 2. Updating the Google Code svn with the 14.1 changes but not make a > package: This would be trivial. I have write access to the SVN repo > so I can update sbopkg in the source tree so it works with 14.1 and > just not worry about the updated package. Let folks pull from SVN in > other words. I'll probably do this no matter what since it's easy to > do. > > 3. Moving the Google Code svn repo over to Github: Similar to #2. > I've slowly gotten accustomed to Git (way behind most of you, I'm > sure) and perhaps it make sense to consolidate it there. Part of me > thinks that since sbopkg is just a shell script and some > configuration files, we don't necessarily need a Slackware package > ready to go, although I'm sure that it's easier for new users to > install a package than pull from a git repo. Still, it's fairly easy > to tag a release on github and just let folks grab the tarball and > manually put stuff in the right place. If I did this, someone could > also submit a SlackBuild to SBo to build a package from a tagged > release. Github also makes it easy to host a webpage for sbopkg > (which Willy and I do for the MSB project) and since I own the > domain, I could point sbopkg.org to the github webpage. > > As far as the future goes, unfortunately, I just don't have time to > actively maintain and develop sbopkg. I'm happy to keep it in the > Google Code SVN repo or host it in a Github repo but in the event > future bugfixes etc. are necessary, I won't be able to focus on them > quickly and timely. Perhaps someone could offer to step up and take > over maintenance and development. Perhaps folks have moved on to > other tools and sbopkg is not needed anymore. Anyway, the point > being that it would be good to hear from folks on their thoughts on > sbopkg, whether they still use it, whether they stopped using it for > something else, etc. Perhaps this input will spur someone to offer to > help take over maintenance and development. I will note that > according to the Google Code download page, the 0.36.0 package has > been downloaded over 15,000 times. > > In the meantime, here is how to get the current sbopkg package > (0.36.0) available on sbopkg.org working with Slackware 14.1: > > First, copy and paste the 14.0 line > in /etc/sbopkg/repos.d/40-sbo.repo and make it 14.1 like so: > > # DO NOT EDIT THIS FILE. CHANGES WILL BE OVERWRITTEN. See the README. > # Repo Branch Description Tag Tool Link CheckGPG > SBo 14.1 "SBo repository for Slackware 14.1" _SBo rsync > slackbuilds.org::slackbuilds/14.1 GPG > SBo 14.0 "SBo repository for Slackware 14.0" _SBo rsync > slackbuilds.org::slackbuilds/14.0 GPG > SBo 13.37 "SBo repository for Slackware 13.37" _SBo rsync > slackbuilds.org::slackbuilds/13.37 GPG > SBo 13.1 "SBo repository for Slackware 13.1" _SBo rsync > slackbuilds.org::slackbuilds/13.1 GPG > SBo 13.0 "SBo repository for Slackware 13.0" _SBo rsync > slackbuilds.org::slackbuilds/13.0 GPG > SBo 12.2 "SBo repository for Slackware 12.2" _SBo rsync > slackbuilds.org::slackbuilds/12.2 GPG > SBo 12.1 "SBo repository for Slackware 12.1" _SBo rsync > slackbuilds.org::slackbuilds/12.1 GPG > SBo 12.0 "SBo repository for Slackware 12.0" _SBo rsync > slackbuilds.org::slackbuilds/12.0 GPG > SBo 11.0 "SBo repository for Slackware 11.0" _SBo rsync > slackbuilds.org::slackbuilds/11.0 GPG > > Second, edit /etc/sbopkg/sbopkg.conf and change REPO_BRANCH in line > 34 to 14.1: > > REPO_BRANCH=${REPO_BRANCH:-14.1} > > That's it! > > I hope everyone is having a great end of year. Thanks! > > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From erectlocution at gmail.com Sun Dec 8 20:17:13 2013 From: erectlocution at gmail.com (Daniel Black) Date: Sun, 08 Dec 2013 12:17:13 -0800 (PST) Subject: [sbopkg-users] Status of next sbopkg release In-Reply-To: <20131208131608.7f577455@home.rlworkman.net> References: <20131208131608.7f577455@home.rlworkman.net> Message-ID: <1386533833741.c54214ad@Nodemailer> For what it's worth, I still use sbopkg quasi-religiously. ? Sent from Mailbox for iPhone On Sun, Dec 8, 2013 at 2:16 PM, Robby Workman wrote: > You still have shell access, although the server name is now > harrier.slackbuilds.org, and I'll mail privately with details. > -RW > On Sun, 08 Dec 2013 01:00:22 -0500 > Chess Griffin wrote: >> Howdy folks- >> >> I thought I'd email the list to let folks know about the status of >> the next sbopkg release. >> >> As some of you may recall, I 'retired' from sbopkg development a few >> years ago and since that time the project had been taken up by my >> original sbopkg co-developers slakmagik and Maurio Giachero. I >> believe Mauro stopped using Slackware some time back but slakmagik >> has still been around and posted to this list as recently as this >> past July. He's done a fantastic job keeping sbopkg updated and >> making releases alongside new Slackware versions. Thank you, >> Slakmagik! I've emailed him a couple of times over the last 3-4 >> months about a new sbopkg release but have not gotten a reply. I'm >> hoping he'll see this post to the list and respond. >> >> As it stands now, the current sbopkg package available on the >> sbopkg.org website (and on the Google Code site) won't work with 14.1 >> without some minor modifications to the configuration files (see >> below for how to get the current sbopkg package working with 14.1). >> The source needs to be updated and a few minor issues posted in the >> Google Code issue tracker need to be addressed. >> >> So, here are options I'm thinking about (input welcome): >> >> 1. Staying with the current hosting and release system: I don't >> know if I still have access to the cardinal server (where sbopkg.org >> is hosted) to update the website when a new package is ready. I'll >> also need to figure out (or recreate) our release process. We had >> scripted some things to update the ChangeLog and make the man pages >> and package it all up in a Slackware package and source tarball. All >> of this will take some time. December is my super-busy time at work >> plus we have the holidays and all that. >> >> 2. Updating the Google Code svn with the 14.1 changes but not make a >> package: This would be trivial. I have write access to the SVN repo >> so I can update sbopkg in the source tree so it works with 14.1 and >> just not worry about the updated package. Let folks pull from SVN in >> other words. I'll probably do this no matter what since it's easy to >> do. >> >> 3. Moving the Google Code svn repo over to Github: Similar to #2. >> I've slowly gotten accustomed to Git (way behind most of you, I'm >> sure) and perhaps it make sense to consolidate it there. Part of me >> thinks that since sbopkg is just a shell script and some >> configuration files, we don't necessarily need a Slackware package >> ready to go, although I'm sure that it's easier for new users to >> install a package than pull from a git repo. Still, it's fairly easy >> to tag a release on github and just let folks grab the tarball and >> manually put stuff in the right place. If I did this, someone could >> also submit a SlackBuild to SBo to build a package from a tagged >> release. Github also makes it easy to host a webpage for sbopkg >> (which Willy and I do for the MSB project) and since I own the >> domain, I could point sbopkg.org to the github webpage. >> >> As far as the future goes, unfortunately, I just don't have time to >> actively maintain and develop sbopkg. I'm happy to keep it in the >> Google Code SVN repo or host it in a Github repo but in the event >> future bugfixes etc. are necessary, I won't be able to focus on them >> quickly and timely. Perhaps someone could offer to step up and take >> over maintenance and development. Perhaps folks have moved on to >> other tools and sbopkg is not needed anymore. Anyway, the point >> being that it would be good to hear from folks on their thoughts on >> sbopkg, whether they still use it, whether they stopped using it for >> something else, etc. Perhaps this input will spur someone to offer to >> help take over maintenance and development. I will note that >> according to the Google Code download page, the 0.36.0 package has >> been downloaded over 15,000 times. >> >> In the meantime, here is how to get the current sbopkg package >> (0.36.0) available on sbopkg.org working with Slackware 14.1: >> >> First, copy and paste the 14.0 line >> in /etc/sbopkg/repos.d/40-sbo.repo and make it 14.1 like so: >> >> # DO NOT EDIT THIS FILE. CHANGES WILL BE OVERWRITTEN. See the README. >> # Repo Branch Description Tag Tool Link CheckGPG >> SBo 14.1 "SBo repository for Slackware 14.1" _SBo rsync >> slackbuilds.org::slackbuilds/14.1 GPG >> SBo 14.0 "SBo repository for Slackware 14.0" _SBo rsync >> slackbuilds.org::slackbuilds/14.0 GPG >> SBo 13.37 "SBo repository for Slackware 13.37" _SBo rsync >> slackbuilds.org::slackbuilds/13.37 GPG >> SBo 13.1 "SBo repository for Slackware 13.1" _SBo rsync >> slackbuilds.org::slackbuilds/13.1 GPG >> SBo 13.0 "SBo repository for Slackware 13.0" _SBo rsync >> slackbuilds.org::slackbuilds/13.0 GPG >> SBo 12.2 "SBo repository for Slackware 12.2" _SBo rsync >> slackbuilds.org::slackbuilds/12.2 GPG >> SBo 12.1 "SBo repository for Slackware 12.1" _SBo rsync >> slackbuilds.org::slackbuilds/12.1 GPG >> SBo 12.0 "SBo repository for Slackware 12.0" _SBo rsync >> slackbuilds.org::slackbuilds/12.0 GPG >> SBo 11.0 "SBo repository for Slackware 11.0" _SBo rsync >> slackbuilds.org::slackbuilds/11.0 GPG >> >> Second, edit /etc/sbopkg/sbopkg.conf and change REPO_BRANCH in line >> 34 to 14.1: >> >> REPO_BRANCH=${REPO_BRANCH:-14.1} >> >> That's it! >> >> I hope everyone is having a great end of year. Thanks! >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From chess at chessgriffin.com Sun Dec 8 22:31:16 2013 From: chess at chessgriffin.com (Chess Griffin) Date: Sun, 08 Dec 2013 17:31:16 -0500 Subject: [sbopkg-users] Status of next sbopkg release In-Reply-To: <20131208131608.7f577455@home.rlworkman.net> References: <0baafcec4b14e3ad13c0268f4360fa88@eumx.net> <20131208131608.7f577455@home.rlworkman.net> Message-ID: On 08.12.2013 14:16, Robby Workman wrote: > You still have shell access, although the server name is now > harrier.slackbuilds.org, and I'll mail privately with details. > > -RW > Doh, of course, I knew it was harrier. Must have been the beers talking. ;-) Thanks, Robby. -- Chess Griffin From mfilpot at gmail.com Sun Dec 8 23:23:18 2013 From: mfilpot at gmail.com (Matthew Fillpot) Date: Sun, 8 Dec 2013 16:23:18 -0700 Subject: [sbopkg-users] Status of next sbopkg release In-Reply-To: <0baafcec4b14e3ad13c0268f4360fa88@eumx.net> References: <0baafcec4b14e3ad13c0268f4360fa88@eumx.net> Message-ID: On Dec 7, 2013 11:00 PM, "Chess Griffin" wrote: > > Howdy folks- > > I thought I'd email the list to let folks know about the status of the next sbopkg release. > > As some of you may recall, I 'retired' from sbopkg development a few years ago and since that time the project had been taken up by my original sbopkg co-developers slakmagik and Maurio Giachero. I believe Mauro stopped using Slackware some time back but slakmagik has still been around and posted to this list as recently as this past July. He's done a fantastic job keeping sbopkg updated and making releases alongside new Slackware versions. Thank you, Slakmagik! I've emailed him a couple of times over the last 3-4 months about a new sbopkg release but have not gotten a reply. I'm hoping he'll see this post to the list and respond. > > As it stands now, the current sbopkg package available on the sbopkg.orgwebsite (and on the Google Code site) won't work with 14.1 without some minor modifications to the configuration files (see below for how to get the current sbopkg package working with 14.1). The source needs to be updated and a few minor issues posted in the Google Code issue tracker need to be addressed. > > So, here are options I'm thinking about (input welcome): > > 1. Staying with the current hosting and release system: I don't know if I still have access to the cardinal server (where sbopkg.org is hosted) to update the website when a new package is ready. I'll also need to figure out (or recreate) our release process. We had scripted some things to update the ChangeLog and make the man pages and package it all up in a Slackware package and source tarball. All of this will take some time. December is my super-busy time at work plus we have the holidays and all that. > > 2. Updating the Google Code svn with the 14.1 changes but not make a package: This would be trivial. I have write access to the SVN repo so I can update sbopkg in the source tree so it works with 14.1 and just not worry about the updated package. Let folks pull from SVN in other words. I'll probably do this no matter what since it's easy to do. > > 3. Moving the Google Code svn repo over to Github: Similar to #2. I've slowly gotten accustomed to Git (way behind most of you, I'm sure) and perhaps it make sense to consolidate it there. Part of me thinks that since sbopkg is just a shell script and some configuration files, we don't necessarily need a Slackware package ready to go, although I'm sure that it's easier for new users to install a package than pull from a git repo. Still, it's fairly easy to tag a release on github and just let folks grab the tarball and manually put stuff in the right place. If I did this, someone could also submit a SlackBuild to SBo to build a package from a tagged release. Github also makes it easy to host a webpage for sbopkg (which Willy and I do for the MSB project) and since I own the domain, I could point sbopkg.org to the github webpage. > > As far as the future goes, unfortunately, I just don't have time to actively maintain and develop sbopkg. I'm happy to keep it in the Google Code SVN repo or host it in a Github repo but in the event future bugfixes etc. are necessary, I won't be able to focus on them quickly and timely. Perhaps someone could offer to step up and take over maintenance and development. Perhaps folks have moved on to other tools and sbopkg is not needed anymore. Anyway, the point being that it would be good to hear from folks on their thoughts on sbopkg, whether they still use it, whether they stopped using it for something else, etc. Perhaps this input will spur someone to offer to help take over maintenance and development. I will note that according to the Google Code download page, the 0.36.0 package has been downloaded over 15,000 times. > > In the meantime, here is how to get the current sbopkg package (0.36.0) available on sbopkg.org working with Slackware 14.1: > > First, copy and paste the 14.0 line in /etc/sbopkg/repos.d/40-sbo.repo and make it 14.1 like so: > > # DO NOT EDIT THIS FILE. CHANGES WILL BE OVERWRITTEN. See the README. > # Repo Branch Description Tag Tool Link CheckGPG > SBo 14.1 "SBo repository for Slackware 14.1" _SBo rsync slackbuilds.org::slackbuilds/14.1 GPG > SBo 14.0 "SBo repository for Slackware 14.0" _SBo rsync slackbuilds.org::slackbuilds/14.0 GPG > SBo 13.37 "SBo repository for Slackware 13.37" _SBo rsync slackbuilds.org::slackbuilds/13.37 GPG > SBo 13.1 "SBo repository for Slackware 13.1" _SBo rsync slackbuilds.org::slackbuilds/13.1 GPG > SBo 13.0 "SBo repository for Slackware 13.0" _SBo rsync slackbuilds.org::slackbuilds/13.0 GPG > SBo 12.2 "SBo repository for Slackware 12.2" _SBo rsync slackbuilds.org::slackbuilds/12.2 GPG > SBo 12.1 "SBo repository for Slackware 12.1" _SBo rsync slackbuilds.org::slackbuilds/12.1 GPG > SBo 12.0 "SBo repository for Slackware 12.0" _SBo rsync slackbuilds.org::slackbuilds/12.0 GPG > SBo 11.0 "SBo repository for Slackware 11.0" _SBo rsync slackbuilds.org::slackbuilds/11.0 GPG > > Second, edit /etc/sbopkg/sbopkg.conf and change REPO_BRANCH in line 34 to 14.1: > > REPO_BRANCH=${REPO_BRANCH:-14.1} > > That's it! > > I hope everyone is having a great end of year. Thanks! > > > -- > Chess Griffin > _______________________________________________ > sbopkg-users mailing list > sbopkg-users at sbopkg.org > http://sbopkg.org/mailman/listinfo/sbopkg-users I still use Sbopkg and am willing to assist or take over maintenance if necessary. Although I will need to read all of the script to better understand the functions prior to taking action. -------------- next part -------------- An HTML attachment was scrubbed... URL: From williams.jayson at gmail.com Mon Dec 9 02:49:44 2013 From: williams.jayson at gmail.com (Jayson Williams) Date: Sun, 8 Dec 2013 21:49:44 -0500 Subject: [sbopkg-users] Status of next sbopkg release In-Reply-To: <0baafcec4b14e3ad13c0268f4360fa88@eumx.net> References: <0baafcec4b14e3ad13c0268f4360fa88@eumx.net> Message-ID: Though I don't believe knowledge wise that I am able to efficiently maintain sbopkb, I would be willing to volunteer to work alongside the final maintainer as an apprentice of sorts, to add to the pool of users able to take on the task maintainer at some point. Its not much, but may help avoid a similar situation in the future. JW _________________________ > sbopkg-users mailing list > sbopkg-users at sbopkg.org > http://sbopkg.org/mailman/listinfo/sbopkg-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mfilpot at gmail.com Mon Dec 9 04:46:09 2013 From: mfilpot at gmail.com (Matthew Fillpot) Date: Sun, 8 Dec 2013 21:46:09 -0700 Subject: [sbopkg-users] Status of next sbopkg release In-Reply-To: <0baafcec4b14e3ad13c0268f4360fa88@eumx.net> References: <0baafcec4b14e3ad13c0268f4360fa88@eumx.net> Message-ID: On Sat, Dec 7, 2013 at 11:00 PM, Chess Griffin wrote: > Howdy folks- > > I thought I'd email the list to let folks know about the status of the next > sbopkg release. > > As some of you may recall, I 'retired' from sbopkg development a few years > ago and since that time the project had been taken up by my original sbopkg > co-developers slakmagik and Maurio Giachero. I believe Mauro stopped using > Slackware some time back but slakmagik has still been around and posted to > this list as recently as this past July. He's done a fantastic job keeping > sbopkg updated and making releases alongside new Slackware versions. Thank > you, Slakmagik! I've emailed him a couple of times over the last 3-4 months > about a new sbopkg release but have not gotten a reply. I'm hoping he'll > see this post to the list and respond. > > As it stands now, the current sbopkg package available on the sbopkg.org > website (and on the Google Code site) won't work with 14.1 without some > minor modifications to the configuration files (see below for how to get the > current sbopkg package working with 14.1). The source needs to be updated > and a few minor issues posted in the Google Code issue tracker need to be > addressed. > > So, here are options I'm thinking about (input welcome): > > 1. Staying with the current hosting and release system: I don't know if I > still have access to the cardinal server (where sbopkg.org is hosted) to > update the website when a new package is ready. I'll also need to figure > out (or recreate) our release process. We had scripted some things to > update the ChangeLog and make the man pages and package it all up in a > Slackware package and source tarball. All of this will take some time. > December is my super-busy time at work plus we have the holidays and all > that. > > 2. Updating the Google Code svn with the 14.1 changes but not make a > package: This would be trivial. I have write access to the SVN repo so I > can update sbopkg in the source tree so it works with 14.1 and just not > worry about the updated package. Let folks pull from SVN in other words. > I'll probably do this no matter what since it's easy to do. > > 3. Moving the Google Code svn repo over to Github: Similar to #2. I've > slowly gotten accustomed to Git (way behind most of you, I'm sure) and > perhaps it make sense to consolidate it there. Part of me thinks that since > sbopkg is just a shell script and some configuration files, we don't > necessarily need a Slackware package ready to go, although I'm sure that > it's easier for new users to install a package than pull from a git repo. > Still, it's fairly easy to tag a release on github and just let folks grab > the tarball and manually put stuff in the right place. If I did this, > someone could also submit a SlackBuild to SBo to build a package from a > tagged release. Github also makes it easy to host a webpage for sbopkg > (which Willy and I do for the MSB project) and since I own the domain, I > could point sbopkg.org to the github webpage. As for your options, option 3 is my preference because it includes a webpage bugtracker and nearly all required tools. As for having a prepared package, you could either store it within a repository, share it via dropbox or many other options that do not require hosting a domain. I am currently testing svn2git to see what steps would be required to convert the googlecode svn repo to a github repo. -- -Thank You, -Matthew Fillpot -Slackware Documentation Project - Staff Editor - http://docs.slackware.com/wiki:user:mfillpot -Linux.com - Moderator - https://www.linux.com/forums/person/198 From chess at chessgriffin.com Mon Dec 9 12:42:10 2013 From: chess at chessgriffin.com (Chess Griffin) Date: Mon, 09 Dec 2013 07:42:10 -0500 Subject: [sbopkg-users] Status of next sbopkg release In-Reply-To: References: <0baafcec4b14e3ad13c0268f4360fa88@eumx.net> Message-ID: On 08.12.2013 23:46, Matthew Fillpot wrote: > > As for your options, option 3 is my preference because it includes a > webpage bugtracker and nearly all required tools. As for having a > prepared package, you could either store it within a repository, share > it via dropbox or many other options that do not require hosting a > domain. > > I am currently testing svn2git to see what steps would be required to > convert the googlecode svn repo to a github repo. (resending since I accidentally sent the first reply from another email address not subscribed to the list) Thanks, Matthew, and thanks to everyone who has replied, both on and off list. svn2git works well, I used it to bring mashpodder over from Google Code to Github. I'm working on getting the next release done, hopefully today. Once that is out, I'll take a look at the various options out there. Cheers! -- Chess Griffin From chess at chessgriffin.com Mon Dec 9 15:31:13 2013 From: chess at chessgriffin.com (Chess Griffin) Date: Mon, 09 Dec 2013 10:31:13 -0500 Subject: [sbopkg-users] Sbopkg 0l37.0 released Message-ID: Here is an updated sbopkg release. Thanks to all the users and contributors! Now that this release is out, I'll take a look at the future in terms of where I'll end up hosting the source code and how we'll handle packages. I may just keep the source maintained and submit a SlackBuild to SBo to handle future packages, especially since Google Code is not allowing new downloads starting January 14, 2014 (although they could be handled in Google Drive or some other location). Either way, I'll post something to the list at some point in the near future. sbopkg 0.37.0 (2013-12-09 15:10 UTC) FEATURES * This release of sbopkg is Slackware 14.1-ready. Congrats to the entire Slackware team for another great release! * Sbopkg now has a -B flag which will allow the user to process the queue from the command line in 'bulk' without confirmation first. MODIFICATIONS * No other modifications have been made. -- Chess Griffin From chess at chessgriffin.com Mon Dec 9 15:34:15 2013 From: chess at chessgriffin.com (Chess Griffin) Date: Mon, 09 Dec 2013 10:34:15 -0500 Subject: [sbopkg-users] Sbopkg 0l37.0 released In-Reply-To: References: Message-ID: <958e82229cbf83e4c636cf916c7b3daa@eumx.net> On 09.12.2013 10:31, Chess Griffin wrote: > Here is an updated sbopkg release. Not sure how that subject line got mangled. Guess I haven't had my fill of coffee yet! Should be 0.37.0. ;-) -- Chess Griffin From phillip.c.warner at gmail.com Sat Dec 14 03:46:24 2013 From: phillip.c.warner at gmail.com (Phillip Warner) Date: Fri, 13 Dec 2013 22:46:24 -0500 Subject: [sbopkg-users] Sbopkg 0l37.0 released In-Reply-To: <958e82229cbf83e4c636cf916c7b3daa@eumx.net> References: <958e82229cbf83e4c636cf916c7b3daa@eumx.net> Message-ID: Thanks for the update! One small change I would recommend to be added to the 50-default.renames: flash-player-plugin=flashplayer-plugin --PW From jbernts at broadpark.no Wed Dec 18 12:33:04 2013 From: jbernts at broadpark.no (Jostein Berntsen) Date: Wed, 18 Dec 2013 13:33:04 +0100 Subject: [sbopkg-users] New feauture: List packages by author Message-ID: <20131218123304.GA1600@jostein> This would be really useful for maintaining SlackBuilds for those who have a lot of packages to update. Jostein From dave at dawoodfall.net Wed Dec 18 16:24:03 2013 From: dave at dawoodfall.net (David Woodfall) Date: Wed, 18 Dec 2013 16:24:03 +0000 Subject: [sbopkg-users] New feauture: List packages by author In-Reply-To: <20131218123304.GA1600@jostein> References: <20131218123304.GA1600@jostein> Message-ID: <20131218162403.GC1399@Blackswan> On (18/12/13 13:33), Jostein Berntsen put forth the proposition: >This would be really useful for maintaining SlackBuilds for those who have a >lot of packages to update. > >Jostein Is this any use to you? Edit NAME, ROOT and REPO, and it will copy your own slackbuilds do a folder for easier sifting: ======================= #!/bin/sh set -e sbopkg -r NAME="Woodfall" REPO=14.1 ROOT=/root/14.1 mkdir -p $ROOT cd $ROOT for i in $(grep -l $NAME /var/lib/sbopkg/SBo/$REPO/*/*/*.info) do dir=$(dirname $i) cat=$(echo $dir | cut -d'/' -f7) prgnam=$(echo $dir | cut -d'/' -f6) mkdir -p $cat/$prgnam cp -vr $dir $cat let num=$num+1 done echo $num packages ======================== All the best Dave From dave at dawoodfall.net Thu Dec 19 00:47:50 2013 From: dave at dawoodfall.net (David Woodfall) Date: Thu, 19 Dec 2013 00:47:50 +0000 Subject: [sbopkg-users] New feauture: List packages by author In-Reply-To: <20131218162403.GC1399@Blackswan> References: <20131218123304.GA1600@jostein> <20131218162403.GC1399@Blackswan> Message-ID: <20131219004749.GH1399@Blackswan> On (18/12/13 16:24), Dave Woodfall put forth the proposition: >On (18/12/13 13:33), Jostein Berntsen put forth the proposition: >>This would be really useful for maintaining SlackBuilds for those who have a >>lot of packages to update. >> >>Jostein > >Is this any use to you? Edit NAME, ROOT and REPO, and it will copy >your own slackbuilds do a folder for easier sifting: > >======================= >#!/bin/sh > >set -e > >sbopkg -r >NAME="Woodfall" >REPO=14.1 >ROOT=/root/14.1 >mkdir -p $ROOT >cd $ROOT > >for i in $(grep -l $NAME /var/lib/sbopkg/SBo/$REPO/*/*/*.info) >do > dir=$(dirname $i) > cat=$(echo $dir | cut -d'/' -f7) > prgnam=$(echo $dir | cut -d'/' -f6) > mkdir -p $cat/$prgnam > > cp -vr $dir $cat > let num=$num+1 >done > >echo $num packages >======================== Replace 'mkdir -p $cat/$prgnam' with: mkdir -p $cat -Dave From chess at chessgriffin.com Thu Dec 19 03:16:22 2013 From: chess at chessgriffin.com (Chess Griffin) Date: Wed, 18 Dec 2013 22:16:22 -0500 Subject: [sbopkg-users] New feauture: List packages by author In-Reply-To: <20131219004749.GH1399@Blackswan> References: <20131218123304.GA1600@jostein> <20131218162403.GC1399@Blackswan> <20131219004749.GH1399@Blackswan> Message-ID: <55c5eba0f33273ff6679e030762990c0@eumx.net> On 18.12.2013 19:47, David Woodfall wrote: > On (18/12/13 16:24), Dave Woodfall put forth the > proposition: >> On (18/12/13 13:33), Jostein Berntsen put forth >> the proposition: >>> This would be really useful for maintaining SlackBuilds for those who >>> have a >>> lot of packages to update. >>> >>> Jostein >> >> Is this any use to you? Edit NAME, ROOT and REPO, and it will copy >> your own slackbuilds do a folder for easier sifting: >> Jostein, Thank you for the suggestion. I think something like this is definitely best handled with a separate script like what David posted. I'm sure you could even redirect the list of packages to a text file as an initial draft of a sbopkg queuefile or as the starting point to run the packages through the 'sqg' helper script to come up with the list of REQUIRES etc. There are a variety of possibilities I think. -- Chess Griffin From jbernts at broadpark.no Thu Dec 19 19:12:40 2013 From: jbernts at broadpark.no (Jostein Berntsen) Date: Thu, 19 Dec 2013 20:12:40 +0100 Subject: [sbopkg-users] New feauture: List packages by author In-Reply-To: <20131218162403.GC1399@Blackswan> References: <20131218123304.GA1600@jostein> <20131218162403.GC1399@Blackswan> Message-ID: <20131219191240.GA28198@jostein> On 18.12.13,16:24, David Woodfall wrote: > On (18/12/13 13:33), Jostein Berntsen put forth the proposition: > >This would be really useful for maintaining SlackBuilds for those who have a > >lot of packages to update. > > > >Jostein > > Is this any use to you? Edit NAME, ROOT and REPO, and it will copy > your own slackbuilds do a folder for easier sifting: > > ======================= > #!/bin/sh > > set -e > > sbopkg -r > NAME="Woodfall" > REPO=14.1 > ROOT=/root/14.1 > mkdir -p $ROOT > cd $ROOT > > for i in $(grep -l $NAME /var/lib/sbopkg/SBo/$REPO/*/*/*.info) > do > dir=$(dirname $i) > cat=$(echo $dir | cut -d'/' -f7) > prgnam=$(echo $dir | cut -d'/' -f6) > mkdir -p $cat/$prgnam > > cp -vr $dir $cat > let num=$num+1 > done > > echo $num packages > ======================== > Thanks! This inspired me to make my own version of your script which gives me the output I need: ========================= #!/bin/sh set -e sbopkg -r -q NAME="Jostein Berntsen" REPO=14.1 ROOT=/home/jostein/14.1/jb mkdir -p $ROOT cd $ROOT echo for i in $(grep -l "$NAME" /var/lib/sbopkg/SBo/$REPO/*/*/*.info) do let num=$num+1 echo $num. dir=$(dirname `pwd`$i | cut -d"/" -f11) pack=$(cat $i | sed '/PRGNAM\|VERSION\|HOMEPAGE/!d' $i | paste -d "," -s) echo $dir: $pack echo done echo $num packages authored by $NAME ========================= Regards, Jostein