From cotterochan at googlemail.com Mon Dec 1 10:43:00 2008 From: cotterochan at googlemail.com (samac) Date: Mon, 1 Dec 2008 02:43:00 -0800 (PST) Subject: Sbopkg and pending Slackware release In-Reply-To: References: Message-ID: Hi Chess As I have said before, sbopkg makes using slackbuilds easy. However, I would like to ask if either of the following were possible to enhance this already fine package. 1. A slackbuild on the slackbuilds site, so that sbopkg could detect, build and upgrade itself. 2. Some sort of integration with slackpkg so that one tool could update an entire Slackware system. Regards Steven On Nov 24, 8:09 pm, Chess Griffin wrote: > With Slackware 12.2 on the horizon, I will hold off on integrating any > new features or major additions into sbopkg until after its release. > I am in the process of updating sbopkg for Slackware 12.2 so it will > be ready once the new Slackware release is announced. > > Thanks again for all the contributions and support. I look forward to > continue hacking on and improving sbopkg after the release of > Slackware 12.2. > > And to those in the US - Happy Thanksgiving! > > Chess From chess.griffin at gmail.com Thu Dec 4 17:35:09 2008 From: chess.griffin at gmail.com (Chess Griffin) Date: Thu, 4 Dec 2008 09:35:09 -0800 (PST) Subject: [sbopkg-discuss] Sbopkg 0.14.1 Released - minor bugfix only Message-ID: <4becffec-f626-4e5e-a618-2e0eb892e04e@k8g2000yqn.googlegroups.com> I thought I would push out a minor bug fix release version 0.14.1 -- consider this release the last version of sbopkg that will default to supporting Slackware 12.1 (pending any other bug fixes I can to before Slackware 12.2 arrives). If sbopkg 0.14.0 is working ok for you now, you can hold off upgrading until a new version is released after Slackware 12.2 since that will also have the same fixes listed below. This new release includes the following improvements: * Fix issue where certain package names where showing up incorrectly in the 'install' option - i.e. mplayer instead of mplayer-codecs-all. Thanks to necropresto for the bug report. * A few little cleanups and cruft-removal. Please check out the included ChangeLog for more details. As always, please report any bugs to me via email, the sbopkg mailing list, or, using the Issue tracker on the project's Google Code website. I can also be found in #sbopkg, #slackbuilds, and ##slackware on freenode. A noarch package and source tarball for version 0.14.1 can be found at the sbopkg project website: http://www.sbopkg.org Thanks! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group. To post to this group, send email to sbopkg-discuss at googlegroups.com To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en -~----------~----~----~----~------~----~------~--~--- From nenad.spirkoski at gmail.com Sat Dec 6 01:34:25 2008 From: nenad.spirkoski at gmail.com (Nenad Spirkoski) Date: Sat, 6 Dec 2008 02:34:25 +0100 Subject: [sbopkg-discuss] Re: Suggestion: Automatic Rebuild of Installed Packages In-Reply-To: <493985B7.3050308@chessgriffin.com> References: <52c7287a-13f0-4bfe-b062-bb1e3f44d700@y1g2000pra.googlegroups.com> <20081204133555.376c637a@liberty.rlwhome.lan> <49383A54.5010701@chessgriffin.com> <2f2c01e40812050504k5e9588c1m5e3a534fe4924c28@mail.gmail.com> <493984EC.20401@chessgriffin.com> <493985B7.3050308@chessgriffin.com> Message-ID: <2f2c01e40812051734r4a02f87by28f789e07a22fdc1@mail.gmail.com> >> Interesting thought. I'll have to test that out. Can you think of a >> case where this may not work? > Answering myself... > > I guess one potential problem could be where a build dep for an > application was later rebuilt and reinstalled by the user _after_ the > application software for which it is a dependency was installed. Like > maybe for a library version bump. The output above wouldn't know that, > and would build the application before the dependency. You are of course right about this scenario... Don't remember having issues because of that kind of problem though. OTOH, I'm basicaly doing it ~ this way on few computers i regulary use (4 laptops and 2 desktops :) (I actually prune the list, excluding some packages and for some packages I install the previously builded package from another computer...) spiki at linette ~ $ ls /var/log/packages/*SBo | wc -l 317 -- http://www.spiki.be I sell frozen yogurt which i call frogurt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group. To post to this group, send email to sbopkg-discuss at googlegroups.com To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en -~----------~----~----~----~------~----~------~--~--- From chess at chessgriffin.com Fri Dec 5 19:49:11 2008 From: chess at chessgriffin.com (Chess Griffin) Date: Fri, 05 Dec 2008 14:49:11 -0500 Subject: [sbopkg-discuss] Re: Suggestion: Automatic Rebuild of Installed Packages In-Reply-To: <493984EC.20401@chessgriffin.com> References: <52c7287a-13f0-4bfe-b062-bb1e3f44d700@y1g2000pra.googlegroups.com> <20081204133555.376c637a@liberty.rlwhome.lan> <49383A54.5010701@chessgriffin.com> <2f2c01e40812050504k5e9588c1m5e3a534fe4924c28@mail.gmail.com> <493984EC.20401@chessgriffin.com> Message-ID: <493985B7.3050308@chessgriffin.com> Chess Griffin wrote: > Nenad Spirkoski wrote: > >> commands such as >> ls -t /var/log/packages/*SBo | cut -d "/" -f5 >> or >> ls -t /var/log/packages/ | grep SBo >> >> will give you listing of SBo packages sorted by installed time... >> which may be "good enought" order for building and upgradepkg >> --install-new >> >> Packages that have build deps were installed after their dependencies... >> Packages that have run time deps only the order isn't important... >> For packages that made into Slackware 12.2 upgradepkg won't install >> the SBo version (and such packages will not be in SBo 12.2 repo >> anyway) >> > > Interesting thought. I'll have to test that out. Can you think of a > case where this may not work? > Answering myself... I guess one potential problem could be where a build dep for an application was later rebuilt and reinstalled by the user _after_ the application software for which it is a dependency was installed. Like maybe for a library version bump. The output above wouldn't know that, and would build the application before the dependency. -- Chess Griffin GPG Key: 0x84F0D7B6 http://www.chessgriffin.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From chess at chessgriffin.com Fri Dec 5 19:45:48 2008 From: chess at chessgriffin.com (Chess Griffin) Date: Fri, 05 Dec 2008 14:45:48 -0500 Subject: [sbopkg-discuss] Re: Suggestion: Automatic Rebuild of Installed Packages In-Reply-To: <2f2c01e40812050504k5e9588c1m5e3a534fe4924c28@mail.gmail.com> References: <52c7287a-13f0-4bfe-b062-bb1e3f44d700@y1g2000pra.googlegroups.com> <20081204133555.376c637a@liberty.rlwhome.lan> <49383A54.5010701@chessgriffin.com> <2f2c01e40812050504k5e9588c1m5e3a534fe4924c28@mail.gmail.com> Message-ID: <493984EC.20401@chessgriffin.com> Nenad Spirkoski wrote: > > commands such as > ls -t /var/log/packages/*SBo | cut -d "/" -f5 > or > ls -t /var/log/packages/ | grep SBo > > will give you listing of SBo packages sorted by installed time... > which may be "good enought" order for building and upgradepkg > --install-new > > Packages that have build deps were installed after their dependencies... > Packages that have run time deps only the order isn't important... > For packages that made into Slackware 12.2 upgradepkg won't install > the SBo version (and such packages will not be in SBo 12.2 repo > anyway) > Interesting thought. I'll have to test that out. Can you think of a case where this may not work? -- Chess Griffin GPG Key: 0x84F0D7B6 http://www.chessgriffin.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From nenad.spirkoski at gmail.com Fri Dec 5 13:04:33 2008 From: nenad.spirkoski at gmail.com (Nenad Spirkoski) Date: Fri, 5 Dec 2008 14:04:33 +0100 Subject: [sbopkg-discuss] Re: Suggestion: Automatic Rebuild of Installed Packages In-Reply-To: <49383A54.5010701@chessgriffin.com> References: <52c7287a-13f0-4bfe-b062-bb1e3f44d700@y1g2000pra.googlegroups.com> <20081204133555.376c637a@liberty.rlwhome.lan> <49383A54.5010701@chessgriffin.com> Message-ID: <2f2c01e40812050504k5e9588c1m5e3a534fe4924c28@mail.gmail.com> > # sbopkg -b "pkg1 pkg2 pkg3" > > and it will build (not install) in that order. By extending it to > installation, you could have: > > # sbopkg -i "dep1 dep2 myfavoritepkg" > Once I get this going, then I might be able to do something similar in > the dialog interface. Perhaps there can be a way for the user to > manually queue up which packages to build and install in the order > presented, like a bulk build/install. This would essentially, put the > dependency resolution on the user, which is what Slackware does already. > :-) I am sure there are some corner cases where this may not work, but > it should cover at least 95% of the software in SBo. commands such as ls -t /var/log/packages/*SBo | cut -d "/" -f5 or ls -t /var/log/packages/ | grep SBo will give you listing of SBo packages sorted by installed time... which may be "good enought" order for building and upgradepkg --install-new Packages that have build deps were installed after their dependencies... Packages that have run time deps only the order isn't important... For packages that made into Slackware 12.2 upgradepkg won't install the SBo version (and such packages will not be in SBo 12.2 repo anyway) -- http://www.spiki.be I sell frozen yogurt which i call frogurt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group. To post to this group, send email to sbopkg-discuss at googlegroups.com To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en -~----------~----~----~----~------~----~------~--~--- From cotterochan at googlemail.com Fri Dec 5 09:47:25 2008 From: cotterochan at googlemail.com (samac) Date: Fri, 5 Dec 2008 01:47:25 -0800 (PST) Subject: [sbopkg-discuss] Re: Suggestion: Automatic Rebuild of Installed Packages In-Reply-To: <49383A54.5010701@chessgriffin.com> References: <52c7287a-13f0-4bfe-b062-bb1e3f44d700@y1g2000pra.googlegroups.com> <20081204133555.376c637a@liberty.rlwhome.lan> <49383A54.5010701@chessgriffin.com> Message-ID: <31830a4e-c8c8-4be5-a565-9e35e3efbe21@v13g2000yqm.googlegroups.com> This sounds workable, guess I will have to draw up a dependency chart for the slackbuilds that I have installed. samac --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group. To post to this group, send email to sbopkg-discuss at googlegroups.com To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en -~----------~----~----~----~------~----~------~--~--- From alkos333 at gmail.com Fri Dec 5 01:42:47 2008 From: alkos333 at gmail.com (alkos333) Date: Thu, 4 Dec 2008 17:42:47 -0800 (PST) Subject: [sbopkg-discuss] Re: Suggestion: Automatic Rebuild of Installed Packages In-Reply-To: <49383A54.5010701@chessgriffin.com> References: <52c7287a-13f0-4bfe-b062-bb1e3f44d700@y1g2000pra.googlegroups.com> <20081204133555.376c637a@liberty.rlwhome.lan> <49383A54.5010701@chessgriffin.com> Message-ID: <23f25113-66c5-486f-973f-cc0402af0c1a@b38g2000prf.googlegroups.com> Yes, This does sound like a very good solution. I was just thinking about this a couple days ago. On Dec 4, 2:15?pm, Chess Griffin wrote: > Robby Workman wrote: > > On Thu, 4 Dec 2008 11:21:04 -0800 (PST) > > samac wrote: > > >> Hi > > >> I don't know if this would be possible, or even desirable, but as > >> Slackware 12.2 is on the horizon it might be worth thinking about. > > >> My thoughts are that once Slackware has been updated to 12.2, I will > >> have to re-build all the slackbuild packages that I have installed, so > >> that they take advantage of the newly installed versions. Could this > >> be automated by having a menu entry similar to "List installed Sbo > >> packages", where it lists all the packages installed and pipes it to > >> the build script, then once all the packages are built, has an option > >> to install. > > >> I know that I could do all of this one item at a time, but I am > >> essentially a lazy person, and as sbopkg has made administrating > >> slackbuilds so easy, I was hoping that this might be a worthwhile > >> improvement. > > > Perhaps a worthy improvement, but without some way to determine the > > order, I'm not sure how doable it is -- e.g. if binX depends on libX, > > then you have to build libX first. ? > > Indeed, that has been the issue so far. ?One improvement I plan to add > after 12.2 is released is the ability to install packages after they are > built using sbopkg's command line interface, and, since it already > builds packages in the order they are listed, you could conceivably > build and install deps and the final pkg in one go. ?So, currently you > can do this: > > # sbopkg -b "pkg1 pkg2 pkg3" > > and it will build (not install) in that order. ?By extending it to > installation, you could have: > > # sbopkg -i "dep1 dep2 myfavoritepkg" > > which would build, and then install, in that order. ?I already have this > working for the most part and will commit the code after 12.2 is released. > > Once I get this going, then I might be able to do something similar in > the dialog interface. ?Perhaps there can be a way for the user to > manually queue up which packages to build and install in the order > presented, like a bulk build/install. ?This would essentially, put the > dependency resolution on the user, which is what Slackware does already. > ?:-) ?I am sure there are some corner cases where this may not work, but > it should cover at least 95% of the software in SBo. > > I have not done any of that work yet, but maybe that is something that > can be put on the TODO. > > -- > Chess Griffin > GPG Key: ?0x84F0D7B6http://www.chessgriffin.com > > ?signature.asc > < 1KViewDownload --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group. To post to this group, send email to sbopkg-discuss at googlegroups.com To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en -~----------~----~----~----~------~----~------~--~--- From rworkman at slackbuilds.org Thu Dec 4 20:32:25 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 4 Dec 2008 14:32:25 -0600 Subject: [sbopkg-discuss] Re: Suggestion: Automatic Rebuild of Installed Packages In-Reply-To: <49383A54.5010701@chessgriffin.com> References: <52c7287a-13f0-4bfe-b062-bb1e3f44d700@y1g2000pra.googlegroups.com> <20081204133555.376c637a@liberty.rlwhome.lan> <49383A54.5010701@chessgriffin.com> Message-ID: <20081204143225.130f15ed@liberty.rlwhome.lan> On Thu, 04 Dec 2008 15:15:16 -0500 Chess Griffin wrote: > Robby Workman wrote: > > On Thu, 4 Dec 2008 11:21:04 -0800 (PST) > > samac wrote: > > > >> Hi > >> > >> I don't know if this would be possible, or even desirable, but as > >> Slackware 12.2 is on the horizon it might be worth thinking about. > >> > >> My thoughts are that once Slackware has been updated to 12.2, I > >> will have to re-build all the slackbuild packages that I have > >> installed, so that they take advantage of the newly installed > >> versions. Could this be automated by having a menu entry similar > >> to "List installed Sbo packages", where it lists all the packages > >> installed and pipes it to the build script, then once all the > >> packages are built, has an option to install. > >> > >> I know that I could do all of this one item at a time, but I am > >> essentially a lazy person, and as sbopkg has made administrating > >> slackbuilds so easy, I was hoping that this might be a worthwhile > >> improvement. > > > > > > Perhaps a worthy improvement, but without some way to determine the > > order, I'm not sure how doable it is -- e.g. if binX depends on > > libX, then you have to build libX first. > > Indeed, that has been the issue so far. One improvement I plan to add > after 12.2 is released is the ability to install packages after they > are built using sbopkg's command line interface, and, since it already > builds packages in the order they are listed, you could conceivably > build and install deps and the final pkg in one go. So, currently you > can do this: > > # sbopkg -b "pkg1 pkg2 pkg3" > > and it will build (not install) in that order. By extending it to > installation, you could have: > > # sbopkg -i "dep1 dep2 myfavoritepkg" > > which would build, and then install, in that order. I already have > this working for the most part and will commit the code after 12.2 is > released. > > Once I get this going, then I might be able to do something similar in > the dialog interface. Perhaps there can be a way for the user to > manually queue up which packages to build and install in the order > presented, like a bulk build/install. This would essentially, put the > dependency resolution on the user, which is what Slackware does > already. :-) I am sure there are some corner cases where this may > not work, but it should cover at least 95% of the software in SBo. > > I have not done any of that work yet, but maybe that is something that > can be put on the TODO. > That sounds reasonable; in that regard, it would behave like the individual pkgtool suite -- files are operated on in the order they're specified on the command line. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From chess at chessgriffin.com Thu Dec 4 20:15:16 2008 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 04 Dec 2008 15:15:16 -0500 Subject: [sbopkg-discuss] Re: Suggestion: Automatic Rebuild of Installed Packages In-Reply-To: <20081204133555.376c637a@liberty.rlwhome.lan> References: <52c7287a-13f0-4bfe-b062-bb1e3f44d700@y1g2000pra.googlegroups.com> <20081204133555.376c637a@liberty.rlwhome.lan> Message-ID: <49383A54.5010701@chessgriffin.com> Robby Workman wrote: > On Thu, 4 Dec 2008 11:21:04 -0800 (PST) > samac wrote: > >> Hi >> >> I don't know if this would be possible, or even desirable, but as >> Slackware 12.2 is on the horizon it might be worth thinking about. >> >> My thoughts are that once Slackware has been updated to 12.2, I will >> have to re-build all the slackbuild packages that I have installed, so >> that they take advantage of the newly installed versions. Could this >> be automated by having a menu entry similar to "List installed Sbo >> packages", where it lists all the packages installed and pipes it to >> the build script, then once all the packages are built, has an option >> to install. >> >> I know that I could do all of this one item at a time, but I am >> essentially a lazy person, and as sbopkg has made administrating >> slackbuilds so easy, I was hoping that this might be a worthwhile >> improvement. > > > Perhaps a worthy improvement, but without some way to determine the > order, I'm not sure how doable it is -- e.g. if binX depends on libX, > then you have to build libX first. Indeed, that has been the issue so far. One improvement I plan to add after 12.2 is released is the ability to install packages after they are built using sbopkg's command line interface, and, since it already builds packages in the order they are listed, you could conceivably build and install deps and the final pkg in one go. So, currently you can do this: # sbopkg -b "pkg1 pkg2 pkg3" and it will build (not install) in that order. By extending it to installation, you could have: # sbopkg -i "dep1 dep2 myfavoritepkg" which would build, and then install, in that order. I already have this working for the most part and will commit the code after 12.2 is released. Once I get this going, then I might be able to do something similar in the dialog interface. Perhaps there can be a way for the user to manually queue up which packages to build and install in the order presented, like a bulk build/install. This would essentially, put the dependency resolution on the user, which is what Slackware does already. :-) I am sure there are some corner cases where this may not work, but it should cover at least 95% of the software in SBo. I have not done any of that work yet, but maybe that is something that can be put on the TODO. -- Chess Griffin GPG Key: 0x84F0D7B6 http://www.chessgriffin.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From treehead at gmail.com Thu Dec 4 19:40:13 2008 From: treehead at gmail.com (cRaig Forrester) Date: Thu, 4 Dec 2008 14:40:13 -0500 Subject: [sbopkg-discuss] Re: Suggestion: Automatic Rebuild of Installed Packages In-Reply-To: <20081204133555.376c637a@liberty.rlwhome.lan> References: <52c7287a-13f0-4bfe-b062-bb1e3f44d700@y1g2000pra.googlegroups.com> <20081204133555.376c637a@liberty.rlwhome.lan> Message-ID: <18846aef0812041140l3698a03duecba612d1c5f8750@mail.gmail.com> /me smells dependency checking... cRaig --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group. To post to this group, send email to sbopkg-discuss at googlegroups.com To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en -~----------~----~----~----~------~----~------~--~--- From rworkman at slackbuilds.org Thu Dec 4 19:35:55 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 4 Dec 2008 13:35:55 -0600 Subject: [sbopkg-discuss] Re: Suggestion: Automatic Rebuild of Installed Packages In-Reply-To: <52c7287a-13f0-4bfe-b062-bb1e3f44d700@y1g2000pra.googlegroups.com> References: <52c7287a-13f0-4bfe-b062-bb1e3f44d700@y1g2000pra.googlegroups.com> Message-ID: <20081204133555.376c637a@liberty.rlwhome.lan> On Thu, 4 Dec 2008 11:21:04 -0800 (PST) samac wrote: > > Hi > > I don't know if this would be possible, or even desirable, but as > Slackware 12.2 is on the horizon it might be worth thinking about. > > My thoughts are that once Slackware has been updated to 12.2, I will > have to re-build all the slackbuild packages that I have installed, so > that they take advantage of the newly installed versions. Could this > be automated by having a menu entry similar to "List installed Sbo > packages", where it lists all the packages installed and pipes it to > the build script, then once all the packages are built, has an option > to install. > > I know that I could do all of this one item at a time, but I am > essentially a lazy person, and as sbopkg has made administrating > slackbuilds so easy, I was hoping that this might be a worthwhile > improvement. Perhaps a worthy improvement, but without some way to determine the order, I'm not sure how doable it is -- e.g. if binX depends on libX, then you have to build libX first. A workaround for most cases is to rebuild everything (as it should build against the older version that's already installed, in most cases), upgrade the packages, then rebuild them again so that they pick up the newer deps. This though is overkill most of the time, at least for upgrades that don't change API/ABI. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From cotterochan at googlemail.com Thu Dec 4 19:21:04 2008 From: cotterochan at googlemail.com (samac) Date: Thu, 4 Dec 2008 11:21:04 -0800 (PST) Subject: [sbopkg-discuss] Suggestion: Automatic Rebuild of Installed Packages Message-ID: <52c7287a-13f0-4bfe-b062-bb1e3f44d700@y1g2000pra.googlegroups.com> Hi I don't know if this would be possible, or even desirable, but as Slackware 12.2 is on the horizon it might be worth thinking about. My thoughts are that once Slackware has been updated to 12.2, I will have to re-build all the slackbuild packages that I have installed, so that they take advantage of the newly installed versions. Could this be automated by having a menu entry similar to "List installed Sbo packages", where it lists all the packages installed and pipes it to the build script, then once all the packages are built, has an option to install. I know that I could do all of this one item at a time, but I am essentially a lazy person, and as sbopkg has made administrating slackbuilds so easy, I was hoping that this might be a worthwhile improvement. Regards samac --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group. To post to this group, send email to sbopkg-discuss at googlegroups.com To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en -~----------~----~----~----~------~----~------~--~--- From chess at chessgriffin.com Thu Dec 11 02:45:58 2008 From: chess at chessgriffin.com (Chess Griffin) Date: Wed, 10 Dec 2008 21:45:58 -0500 Subject: [sbopkg-discuss] Sbopkg 0.15.0 Released Message-ID: <20081211024558.GA21985@localhost> A new version 0.15.0 of sbopkg has been released with support for the new and shiny Slackware 12.2! I would like to first congratulate Pat and the rest of the Slackware crew on another outstanding release. Clearly, Slackware 12.2 will be the best release yet. Thank you for all the hard work at providing everyone with a stable, solid, and fun Linux distribution to enjoy. Second, I would like to thank the SBo admins for doing such a great job with maintaining SlackBuilds.org and also all the individual maintainers of the contributed SlackBuild scripts at SBo for helping the admins get everything ready for the new release. Sbopkg is only as good as SlackBuilds.org itself and personally, I think SlackBuilds.org rocks. :-) This new release includes the following improvements: * Slackware 12.2 is now the default Slackware version selected when using sbopkg. * Fix an issue where sometimes a built package was incorrectly listed in the software info item menu, i.e. mplayer-codecs-all instead of mplayer. Thanks to necropresto for the bug report. * Add --no-owner to default rsync flags to avoid having the local SBo repo tagged with owner 1016 permissions. Thanks to Pierre Cazenave for the bug report and Erik Hanson for the suggested solution. Please check out the included ChangeLog for more details. As always, please report any bugs to me via email, the sbopkg mailing list, or, using the Issue tracker on the project's Google Code website. I can also be found in #sbopkg, #slackbuilds, and ##slackware on freenode. A noarch package and source tarball for version 0.15.0 can be found at the sbopkg project website: http://www.sbopkg.org Finally, now that Slackware 12.2 has been released, I plan to start working on some new features and enhancements to sbopkg. Thanks! -- Chess Griffin | () ascii ribbon campaign public key: 0x84F0D7B6 | /\ www.asciiribbon.org http://www.chessgriffin.com | against html email -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From chess.griffin at gmail.com Wed Dec 17 00:59:56 2008 From: chess.griffin at gmail.com (Chess Griffin) Date: Tue, 16 Dec 2008 19:59:56 -0500 Subject: [sbopkg-discuss] Updates in SVN In-Reply-To: <20081215172826.GA6655@localhost> References: <20081215172826.GA6655@localhost> Message-ID: <20081217005956.GA23232@localhost> * Chess Griffin [2008-12-15 12:28:26]: > I have committed some code to SVN that will now allow the user to > build /and/ install from the command line, using a new -i switch. > Just like with the current -b (build) switch, the packages are > processed in the order listed in quotes, so it is possible to do this: > These updates have been substantially modified and there is now a 'build/install' queue available in the dialog interface. It's a bit rough at the moment, but it's working so far in my testing. This queue allows the user to select more than one package to build, and optionally install, from within the dialog interface. The user can still build packages on a case-by-case basis as in the past. A result of these updates is that the build process no longer takes place within the dialog. It will switch over to a terminal to build/install, and then switch back to the dialog once the build/install queue has been processed. If you have time to check it out from SVN and test, let me know how it works/breaks. :-) -- Chess Griffin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From chess.griffin at gmail.com Mon Dec 15 17:28:26 2008 From: chess.griffin at gmail.com (Chess Griffin) Date: Mon, 15 Dec 2008 12:28:26 -0500 Subject: Updates in SVN Message-ID: <20081215172826.GA6655@localhost> I have committed some code to SVN that will now allow the user to build /and/ install from the command line, using a new -i switch. Just like with the current -b (build) switch, the packages are processed in the order listed in quotes, so it is possible to do this: # sbopkg -i "imlib2 giblib feh" since this is the required build order for feh (as an example). This new commnad will build and then install these three packages, one at a time, in the order listed. I have also added some error checking when using either -b or -i on the command line to alert the user of a listed package does not exist in the repo and lets the user bail out before building or installing. Let me know if you come across any issues. Thanks! -- Chess Griffin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From chess at chessgriffin.com Mon Dec 22 14:12:50 2008 From: chess at chessgriffin.com (Chess Griffin) Date: Mon, 22 Dec 2008 09:12:50 -0500 Subject: [sbopkg-discuss] Re: Sbopkg 0.20.0rc1 available for testing In-Reply-To: <5c9e0e9e-010e-4b90-85d9-4ba368355095@f18g2000vbf.googlegroups.com> References: <20081221171511.GA19697@localhost> <20081222000311.GB26010@localhost> <5c9e0e9e-010e-4b90-85d9-4ba368355095@f18g2000vbf.googlegroups.com> Message-ID: <20081222141249.GA381@localhost> * samac [2008-12-22 02:22:21]: > > Thanks the updates screen now looks fine. A problem with mplayer in > the updates screen. It says it needs to be upgraded to exactly the > same version. The only difference is three errant zeros after the svn > e.g. mplayer-svn_00020081215-i486-1 needs to be upgraded to mplayer- > svn_20081215-i486-1 . > > Steven > Yes, I saw the same thing and it's already fixed in SVN. Thanks! -- Chess Griffin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From cotterochan at googlemail.com Mon Dec 22 10:22:21 2008 From: cotterochan at googlemail.com (samac) Date: Mon, 22 Dec 2008 02:22:21 -0800 (PST) Subject: [sbopkg-discuss] Re: Sbopkg 0.20.0rc1 available for testing In-Reply-To: <20081222000311.GB26010@localhost> References: <20081221171511.GA19697@localhost> <20081222000311.GB26010@localhost> Message-ID: <5c9e0e9e-010e-4b90-85d9-4ba368355095@f18g2000vbf.googlegroups.com> Thanks the updates screen now looks fine. A problem with mplayer in the updates screen. It says it needs to be upgraded to exactly the same version. The only difference is three errant zeros after the svn e.g. mplayer-svn_00020081215-i486-1 needs to be upgraded to mplayer- svn_20081215-i486-1 . Steven On Dec 22, 12:03?am, Chess Griffin wrote: > * samac [2008-12-21 15:47:45]: > > > > > Hi Chess > > > I just queued wxGTK, openal, fftw, freealut, and scorched3d. All built > > and installed perfectly. The updates screen looks a bit screwy though, > > there is an entry for every package installed and several lines for > > each as well. > > > Keep up the good work. > > > Steven > > Steven, thanks for the report. ?Yes, the 'verbose' update screen is > normal for sbopkg from SVN and RC. ?You can comment out the > UPDATE_DEBUG=1 at line 46 in /usr/bin/sbopkg and it will look normal. > > Thanks again! > > -- > Chess Griffin > > ?application_pgp-signature_part > < 1KViewDownload --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group. To post to this group, send email to sbopkg-discuss at googlegroups.com To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en -~----------~----~----~----~------~----~------~--~--- From chess at chessgriffin.com Mon Dec 22 00:03:11 2008 From: chess at chessgriffin.com (Chess Griffin) Date: Sun, 21 Dec 2008 19:03:11 -0500 Subject: [sbopkg-discuss] Re: Sbopkg 0.20.0rc1 available for testing In-Reply-To: References: <20081221171511.GA19697@localhost> Message-ID: <20081222000311.GB26010@localhost> * samac [2008-12-21 15:47:45]: > > Hi Chess > > I just queued wxGTK, openal, fftw, freealut, and scorched3d. All built > and installed perfectly. The updates screen looks a bit screwy though, > there is an entry for every package installed and several lines for > each as well. > > Keep up the good work. > > Steven > Steven, thanks for the report. Yes, the 'verbose' update screen is normal for sbopkg from SVN and RC. You can comment out the UPDATE_DEBUG=1 at line 46 in /usr/bin/sbopkg and it will look normal. Thanks again! -- Chess Griffin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From cotterochan at googlemail.com Sun Dec 21 23:47:45 2008 From: cotterochan at googlemail.com (samac) Date: Sun, 21 Dec 2008 15:47:45 -0800 (PST) Subject: [sbopkg-discuss] Re: Sbopkg 0.20.0rc1 available for testing In-Reply-To: <20081221171511.GA19697@localhost> References: <20081221171511.GA19697@localhost> Message-ID: Hi Chess I just queued wxGTK, openal, fftw, freealut, and scorched3d. All built and installed perfectly. The updates screen looks a bit screwy though, there is an entry for every package installed and several lines for each as well. Keep up the good work. Steven On Dec 21, 5:15?pm, Chess Griffin wrote: > I have uploaded a source tarball and Slackware package for Sbopkg > version 0.20.0 (version bump!) release candidate 1 for testing. ?This > update for sbopkg has many new features and improvements, which I will > describe more specifically in the upcoming release announcement. > However, to entice folks into testing this RC, I will mention that > sbopkg now has a "-i" switch for the cli which will build and install > packages in one go, so with the correct ordering of dependencies, one > might be able to install deps and the final package all at once. > > Additionally, in the dialog interface, there is a new 'build queue' > which will essentially do the same thing -- allow the user to create a > list of packages to build, and optionally install, all at once in the > order listed. > > Two changes to the sbopkg.conf are needed: ?first, the $OUTPUT > variable, which is currently included in the sbopkg.conf file as an > optional, commented out, variable is now required. ?If you are not > already using $OUTPUT, then just uncomment it -- or add it; see the > updated sbopkg.conf(5) man page -- from your current sbopkg.conf file > and you'll be all set. ?Second, $TERMBUILD is now removed since all > building and installing switches out of dialog and processes in the > terminal. ?Showing the build or install process in the dialog > interface was always sort of a hack and was somewhat limiting. > > Anyway, if you would like to test, here are links for the source > tarball and package: > > Package:http://sbopkg.googlecode.com/files/sbopkg-0.20.0rc1-noarch-1_cng.tgz > > Source:http://sbopkg.googlecode.com/files/sbopkg-0.20.0rc1.tar.gz > > Please let me know of any successes or problems. > > Thanks! > > -- > Chess Griffin > > ?application_pgp-signature_part > < 1KViewDownload --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group. To post to this group, send email to sbopkg-discuss at googlegroups.com To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en -~----------~----~----~----~------~----~------~--~--- From chess at chessgriffin.com Sun Dec 21 17:15:12 2008 From: chess at chessgriffin.com (Chess Griffin) Date: Sun, 21 Dec 2008 12:15:12 -0500 Subject: [sbopkg-discuss] Sbopkg 0.20.0rc1 available for testing Message-ID: <20081221171511.GA19697@localhost> I have uploaded a source tarball and Slackware package for Sbopkg version 0.20.0 (version bump!) release candidate 1 for testing. This update for sbopkg has many new features and improvements, which I will describe more specifically in the upcoming release announcement. However, to entice folks into testing this RC, I will mention that sbopkg now has a "-i" switch for the cli which will build and install packages in one go, so with the correct ordering of dependencies, one might be able to install deps and the final package all at once. Additionally, in the dialog interface, there is a new 'build queue' which will essentially do the same thing -- allow the user to create a list of packages to build, and optionally install, all at once in the order listed. Two changes to the sbopkg.conf are needed: first, the $OUTPUT variable, which is currently included in the sbopkg.conf file as an optional, commented out, variable is now required. If you are not already using $OUTPUT, then just uncomment it -- or add it; see the updated sbopkg.conf(5) man page -- from your current sbopkg.conf file and you'll be all set. Second, $TERMBUILD is now removed since all building and installing switches out of dialog and processes in the terminal. Showing the build or install process in the dialog interface was always sort of a hack and was somewhat limiting. Anyway, if you would like to test, here are links for the source tarball and package: Package: http://sbopkg.googlecode.com/files/sbopkg-0.20.0rc1-noarch-1_cng.tgz Source: http://sbopkg.googlecode.com/files/sbopkg-0.20.0rc1.tar.gz Please let me know of any successes or problems. Thanks! -- Chess Griffin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: