From chess.griffin at gmail.com Sat Jan 3 21:53:23 2009 From: chess.griffin at gmail.com (Chess Griffin) Date: Sat, 3 Jan 2009 13:53:23 -0800 (PST) Subject: [sbopkg-discuss] Re: feature idea In-Reply-To: <87tz8hqxfk.fsf@gnu.org> References: <20090101205811.GB22328@localhost> <20090102003243.GB2976@localhost> <5e729854-08f3-4a93-b229-c2435153906a@t11g2000yqg.googlegroups.com> <87tz8hsvp4.fsf@gnu.org> <20090102193650.GA6466@localhost> <8c2c7aa8-62c3-4034-9572-9573b5b5e76a@r15g2000prd.googlegroups.com> <87tz8hqxfk.fsf@gnu.org> Message-ID: On Jan 2, 3:12?pm, Xavier Maillard wrote: > Hi Chess, > > samac writes: > > I was thinking that as soon as you logged in to your user account, I > > usually use KDE, so that for me would be when X started, but this > > wouldn't be suitable for all people. I agree with Xavier that if this > > were to be added it should be an optional addon. My thoughts are that > > people expect to be told when updates are available, they don't expect > > to have to look at change logs. > > Why not do the tip described onto the slackbuilds.org wiki ? I am > doing this and I can see changes on every login and thus decide > wether it is worth upgrading or not. Furthermore, I am not one of > the guy running upgrades (except security advisories) every hour > or so :) > > Your feature request is still a good idea but, please, keep it > optional :) > > Xavier Xavier- Which wiki tip are you referring to? --~--~---------~--~----~------------~-------~--~----~ 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 xma at gnu.org Fri Jan 2 20:12:47 2009 From: xma at gnu.org (Xavier Maillard) Date: Fri, 02 Jan 2009 21:12:47 +0100 Subject: [sbopkg-discuss] Re: feature idea In-Reply-To: <8c2c7aa8-62c3-4034-9572-9573b5b5e76a@r15g2000prd.googlegroups.com> (samac's message of "Fri, 2 Jan 2009 11:52:52 -0800 (PST)") References: <20090101205811.GB22328@localhost> <20090102003243.GB2976@localhost> <5e729854-08f3-4a93-b229-c2435153906a@t11g2000yqg.googlegroups.com> <87tz8hsvp4.fsf@gnu.org> <20090102193650.GA6466@localhost> <8c2c7aa8-62c3-4034-9572-9573b5b5e76a@r15g2000prd.googlegroups.com> Message-ID: <87tz8hqxfk.fsf@gnu.org> Hi Chess, samac writes: > I was thinking that as soon as you logged in to your user account, I > usually use KDE, so that for me would be when X started, but this > wouldn't be suitable for all people. I agree with Xavier that if this > were to be added it should be an optional addon. My thoughts are that > people expect to be told when updates are available, they don't expect > to have to look at change logs. Why not do the tip described onto the slackbuilds.org wiki ? I am doing this and I can see changes on every login and thus decide wether it is worth upgrading or not. Furthermore, I am not one of the guy running upgrades (except security advisories) every hour or so :) Your feature request is still a good idea but, please, keep it optional :) Xavier --~--~---------~--~----~------------~-------~--~----~ 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 Jan 2 19:52:52 2009 From: cotterochan at googlemail.com (samac) Date: Fri, 2 Jan 2009 11:52:52 -0800 (PST) Subject: [sbopkg-discuss] Re: feature idea In-Reply-To: <20090102193650.GA6466@localhost> References: <20090101205811.GB22328@localhost> <20090102003243.GB2976@localhost> <5e729854-08f3-4a93-b229-c2435153906a@t11g2000yqg.googlegroups.com> <87tz8hsvp4.fsf@gnu.org> <20090102193650.GA6466@localhost> Message-ID: <8c2c7aa8-62c3-4034-9572-9573b5b5e76a@r15g2000prd.googlegroups.com> Hi Chess I was thinking that as soon as you logged in to your user account, I usually use KDE, so that for me would be when X started, but this wouldn't be suitable for all people. I agree with Xavier that if this were to be added it should be an optional addon. My thoughts are that people expect to be told when updates are available, they don't expect to have to look at change logs. samac On Jan 2, 7:36?pm, Chess Griffin wrote: > * Xavier Maillard [2009-01-02 14:07:19]: > > > > > Hi samac and sbopkg users, > > > samac writes: > > > > How about running sbopkg at startup, automatically rsyncing and > > > checking for updates and then, notifying you with a pop up box saying > > > that "sbopkg has found updates available." You would then have to run > > > sbopkg to find the updates and their dependencies. > > > If made optional, I would find this perfect but it *must* remain > > optional (I, for sure, won't use such thing otherwise). > > samac, when you say 'running sbopkg at startup' what do you mean > exactly? ?Upon startup of the machine, upon startup of X, upon startup > of sbopkg ... ? > > > > Secondly, could sbopkg do the same job as slackpkg and download and > > > upgrade official Slackware packages? > > > Why not add a menu entry with a choice to run a backgrounded > > slackpkg instance ? Once again, it makes perfectly sense for > > people using slackpkg (which I am not) and it does not bother > > other people (I'd rather want to use slackbuilds). > > > Thank you very much for your attention. > > I understand where you are coming from, samac, but I don't want to > reinvent what slackpkg already does so well. ?PiterPunk has been > working on slackpkg for far longer than I have been hacking on sbopkg, > and slackpkg is much more mature and tested. ?I use slackpkg myself > and it's an excellent tool that rightly was moved into the mainline > tree from /extra. ?Additionally, it seems to me that conceptually the > two scripts really do serve different purposes, although they may do > some things in a similar fashion. ?Ultimately, however, I just think > slackpkg does a great job as is. > > As far as running slackpkg from within sbopkg ... I don't know. ?I'll > have to think about that one, but it seems to add a layer of > complexity on top of slackpkg without really that much benefit. ?It's > just as easy to have two terminals open, one running slackpkg and one > running sbopkg, or to run one first and the other second in a single > terminal. > > Thanks very much for the feedback and suggestions. ?Please do keep the > ideas coming -- I have changed my mind in the past, so it never hurts > to keep reminding me. ?:-) > > -- > 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 Fri Jan 2 19:36:51 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Fri, 2 Jan 2009 14:36:51 -0500 Subject: [sbopkg-discuss] Re: feature idea In-Reply-To: <87tz8hsvp4.fsf@gnu.org> References: <20090101205811.GB22328@localhost> <20090102003243.GB2976@localhost> <5e729854-08f3-4a93-b229-c2435153906a@t11g2000yqg.googlegroups.com> <87tz8hsvp4.fsf@gnu.org> Message-ID: <20090102193650.GA6466@localhost> * Xavier Maillard [2009-01-02 14:07:19]: > > Hi samac and sbopkg users, > > samac writes: > > > How about running sbopkg at startup, automatically rsyncing and > > checking for updates and then, notifying you with a pop up box saying > > that "sbopkg has found updates available." You would then have to run > > sbopkg to find the updates and their dependencies. > > If made optional, I would find this perfect but it *must* remain > optional (I, for sure, won't use such thing otherwise). > samac, when you say 'running sbopkg at startup' what do you mean exactly? Upon startup of the machine, upon startup of X, upon startup of sbopkg ... ? > > Secondly, could sbopkg do the same job as slackpkg and download and > > upgrade official Slackware packages? > > Why not add a menu entry with a choice to run a backgrounded > slackpkg instance ? Once again, it makes perfectly sense for > people using slackpkg (which I am not) and it does not bother > other people (I'd rather want to use slackbuilds). > > Thank you very much for your attention. > I understand where you are coming from, samac, but I don't want to reinvent what slackpkg already does so well. PiterPunk has been working on slackpkg for far longer than I have been hacking on sbopkg, and slackpkg is much more mature and tested. I use slackpkg myself and it's an excellent tool that rightly was moved into the mainline tree from /extra. Additionally, it seems to me that conceptually the two scripts really do serve different purposes, although they may do some things in a similar fashion. Ultimately, however, I just think slackpkg does a great job as is. As far as running slackpkg from within sbopkg ... I don't know. I'll have to think about that one, but it seems to add a layer of complexity on top of slackpkg without really that much benefit. It's just as easy to have two terminals open, one running slackpkg and one running sbopkg, or to run one first and the other second in a single terminal. Thanks very much for the feedback and suggestions. Please do keep the ideas coming -- I have changed my mind in the past, so it never hurts to keep reminding me. :-) -- 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 xma at gnu.org Fri Jan 2 13:07:19 2009 From: xma at gnu.org (Xavier Maillard) Date: Fri, 02 Jan 2009 14:07:19 +0100 Subject: [sbopkg-discuss] Re: feature idea In-Reply-To: <5e729854-08f3-4a93-b229-c2435153906a@t11g2000yqg.googlegroups.com> (samac's message of "Fri, 2 Jan 2009 01:31:50 -0800 (PST)") References: <20090101205811.GB22328@localhost> <20090102003243.GB2976@localhost> <5e729854-08f3-4a93-b229-c2435153906a@t11g2000yqg.googlegroups.com> Message-ID: <87tz8hsvp4.fsf@gnu.org> Hi samac and sbopkg users, samac writes: > How about running sbopkg at startup, automatically rsyncing and > checking for updates and then, notifying you with a pop up box saying > that "sbopkg has found updates available." You would then have to run > sbopkg to find the updates and their dependencies. If made optional, I would find this perfect but it *must* remain optional (I, for sure, won't use such thing otherwise). > Secondly, could sbopkg do the same job as slackpkg and download and > upgrade official Slackware packages? Why not add a menu entry with a choice to run a backgrounded slackpkg instance ? Once again, it makes perfectly sense for people using slackpkg (which I am not) and it does not bother other people (I'd rather want to use slackbuilds). Thank you very much for your attention. Xavier --~--~---------~--~----~------------~-------~--~----~ 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 Jan 2 09:31:50 2009 From: cotterochan at googlemail.com (samac) Date: Fri, 2 Jan 2009 01:31:50 -0800 (PST) Subject: [sbopkg-discuss] Re: feature idea In-Reply-To: <20090102003243.GB2976@localhost> References: <20090101205811.GB22328@localhost> <20090102003243.GB2976@localhost> Message-ID: <5e729854-08f3-4a93-b229-c2435153906a@t11g2000yqg.googlegroups.com> Hi Chess, Hope you had a great festive season. Since we are talking about future ideas, I thought that I might put one or two into the mix. How about running sbopkg at startup, automatically rsyncing and checking for updates and then, notifying you with a pop up box saying that "sbopkg has found updates available." You would then have to run sbopkg to find the updates and their dependencies. Secondly, could sbopkg do the same job as slackpkg and download and upgrade official Slackware packages? This would then allow only one update program on the computer, which would reduce complexity for the user, but more importantly it might make more people use Slackbuilds and therefore increase the package library for both Slackbuilds and Slackware. After all the only real complaint that anyone has about Slackware is the lack of packages available. Whilst you and I know this is a fallacy, newbies do not and anything that makes migrating to Slackware easier for them has to be good. Best wishes samac On Jan 2, 12:32?am, Chess Griffin wrote: > * gmartin [2009-01-01 17:06:32]: > > > > > Chess, that's what I'm interested concurrent builds. As luck would > > have it, I dl'd .20 and found the build queue. It worked very well. > > > Keep up the good work.Happy New Year > > Greg, thanks for the update. ?I'll still keep the concurrent builds in > mind. ?:-) > > -- > 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 Fri Jan 2 00:32:44 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 1 Jan 2009 19:32:44 -0500 Subject: [sbopkg-discuss] Re: feature idea In-Reply-To: References: <20090101205811.GB22328@localhost> Message-ID: <20090102003243.GB2976@localhost> * gmartin [2009-01-01 17:06:32]: > > Chess, that's what I'm interested concurrent builds. As luck would > have it, I dl'd .20 and found the build queue. It worked very well. > > Keep up the good work.Happy New Year > Greg, thanks for the update. I'll still keep the concurrent builds in mind. :-) -- 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 gregmartin1 at gmail.com Thu Jan 1 22:06:32 2009 From: gregmartin1 at gmail.com (gmartin) Date: Thu, 1 Jan 2009 17:06:32 -0500 Subject: [sbopkg-discuss] Re: feature idea In-Reply-To: <20090101205811.GB22328@localhost> References: <20090101205811.GB22328@localhost> Message-ID: Chess, that's what I'm interested concurrent builds. As luck would have it, I dl'd .20 and found the build queue. It worked very well. Keep up the good work.Happy New Year On 1/1/09, Chess Griffin wrote: > * uSlacker [2009-01-01 09:27:55]: > >> >> Chess, great tool, been using it for awhile, but really got into it >> since 12.2. Did all my sbo package upgrades this way. I have a >> thought, let me know if this has been discussed. currently sbopkg >> only support a single instance. I understand that given some of the >> database-like functionality. Would it be possible for the -b option >> to NOT require single-instance? >> >> Obviously I don't understand the internals, but "intuitively" it seems >> possible. >> >> Thoughts? >> >> \\Greg > > Greg, > > Thanks for the kind words and I am glad sbopkg has been working well > for you. As for your feature request, do you mean having more than > one instance of sbopkg running so you could build (using -b) more than > one package at a time? If so, this might be possible -- I've added it > to my TODO list to think about. > > Thanks for the feedback and Happy New Year! > > -- > Chess Griffin > --~--~---------~--~----~------------~-------~--~----~ 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 Jan 1 20:58:11 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 1 Jan 2009 15:58:11 -0500 Subject: [sbopkg-discuss] Re: feature idea In-Reply-To: References: Message-ID: <20090101205811.GB22328@localhost> * uSlacker [2009-01-01 09:27:55]: > > Chess, great tool, been using it for awhile, but really got into it > since 12.2. Did all my sbo package upgrades this way. I have a > thought, let me know if this has been discussed. currently sbopkg > only support a single instance. I understand that given some of the > database-like functionality. Would it be possible for the -b option > to NOT require single-instance? > > Obviously I don't understand the internals, but "intuitively" it seems > possible. > > Thoughts? > > \\Greg Greg, Thanks for the kind words and I am glad sbopkg has been working well for you. As for your feature request, do you mean having more than one instance of sbopkg running so you could build (using -b) more than one package at a time? If so, this might be possible -- I've added it to my TODO list to think about. Thanks for the feedback and Happy New Year! -- 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 gregmartin1 at gmail.com Thu Jan 1 17:27:55 2009 From: gregmartin1 at gmail.com (uSlacker) Date: Thu, 1 Jan 2009 09:27:55 -0800 (PST) Subject: [sbopkg-discuss] feature idea Message-ID: Chess, great tool, been using it for awhile, but really got into it since 12.2. Did all my sbo package upgrades this way. I have a thought, let me know if this has been discussed. currently sbopkg only support a single instance. I understand that given some of the database-like functionality. Would it be possible for the -b option to NOT require single-instance? Obviously I don't understand the internals, but "intuitively" it seems possible. Thoughts? \\Greg --~--~---------~--~----~------------~-------~--~----~ 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 Jan 5 23:11:49 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Mon, 5 Jan 2009 18:11:49 -0500 Subject: [sbopkg-discuss] Re: [Slackbuilds-users] Sbopkg 0.20.0 Released In-Reply-To: <20090105154923.28398e8b@liberty.rlwhome.lan> References: <20090101205319.GA22328@localhost> <20090101221010.GA31384@localhost> <4962607B.8040107@sqdnguns.com> <20090105205217.GA20981@localhost> <20090105154923.28398e8b@liberty.rlwhome.lan> Message-ID: <20090105231149.GB21392@localhost> * Robby Workman [2009-01-05 15:49:23]: > > Heh, oops. My mistake, and Erik fixed it :) > > > > > Also an FYI, anytime I try to build a pkg that has the source on > > > berlios.de, they time out and I have to fetch the source elsewhere. > > > > > > > Hmm... I just build and installed gpodder, which uses berlios.de, and > > it downloaded the source, built, and installed just fine. This was on > > a stock sbopkg 0.20.0. Do you have some specific examples that I can > > try? > > > I suspect that this is a problem specific to Wade's network/ISP; I > can't reproduce it on any berlios stuff either. > > -RW Thanks, Robby. -- 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 rworkman at slackbuilds.org Mon Jan 5 21:49:23 2009 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 5 Jan 2009 15:49:23 -0600 Subject: [sbopkg-discuss] Re: [Slackbuilds-users] Sbopkg 0.20.0 Released In-Reply-To: <20090105205217.GA20981@localhost> References: <20090101205319.GA22328@localhost> <20090101221010.GA31384@localhost> <4962607B.8040107@sqdnguns.com> <20090105205217.GA20981@localhost> Message-ID: <20090105154923.28398e8b@liberty.rlwhome.lan> On Mon, 5 Jan 2009 15:52:17 -0500 Chess Griffin wrote: > This is strange. It appears there is a directory called "ODNE" in the > sakura directory which contains a copy of all the same sbo-related > files. You can see it here: > > ftp://ftp.slackbuilds.org/12.2/system/sakura/ > > I don't think that's supposed to be there and that is what is causing > this problem -- sbopkg is finding two .info files. One of the SBo > admins may need to check this out and remove the extra directory if > it's not needed. Heh, oops. My mistake, and Erik fixed it :) > > Also an FYI, anytime I try to build a pkg that has the source on > > berlios.de, they time out and I have to fetch the source elsewhere. > > > > Hmm... I just build and installed gpodder, which uses berlios.de, and > it downloaded the source, built, and installed just fine. This was on > a stock sbopkg 0.20.0. Do you have some specific examples that I can > try? I suspect that this is a problem specific to Wade's network/ISP; I can't reproduce it on any berlios stuff either. -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 Mon Jan 5 20:52:17 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Mon, 5 Jan 2009 15:52:17 -0500 Subject: [sbopkg-discuss] Re: [Slackbuilds-users] Sbopkg 0.20.0 Released In-Reply-To: <4962607B.8040107@sqdnguns.com> References: <20090101205319.GA22328@localhost> <20090101221010.GA31384@localhost> <4962607B.8040107@sqdnguns.com> Message-ID: <20090105205217.GA20981@localhost> * Wade S Grant [2009-01-05 11:33:15]: > Hi Chess, > > Just found another possible bug or problem with a package. > > When running the Updates option, I get the following: > > sakura: > POTENTIAL UPDATE > Installed version: sakura-2.3.2-i486-1 > Repo version: sakura-2.3.2-i486-1 1 > This is strange. It appears there is a directory called "ODNE" in the sakura directory which contains a copy of all the same sbo-related files. You can see it here: ftp://ftp.slackbuilds.org/12.2/system/sakura/ I don't think that's supposed to be there and that is what is causing this problem -- sbopkg is finding two .info files. One of the SBo admins may need to check this out and remove the extra directory if it's not needed. > Also an FYI, anytime I try to build a pkg that has the source on > berlios.de, they time out and I have to fetch the source elsewhere. > Hmm... I just build and installed gpodder, which uses berlios.de, and it downloaded the source, built, and installed just fine. This was on a stock sbopkg 0.20.0. Do you have some specific examples that I can try? Thanks for the reports. -- 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 Fri Jan 2 00:30:54 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 1 Jan 2009 19:30:54 -0500 Subject: [sbopkg-discuss] Re: [Slackbuilds-users] Sbopkg 0.20.0 Released In-Reply-To: <20090101164454.4b14b58a@liberty.rlwhome.lan> References: <20090101205319.GA22328@localhost> <20090101221010.GA31384@localhost> <20090101164454.4b14b58a@liberty.rlwhome.lan> Message-ID: <20090102003054.GA2976@localhost> * Robby Workman [2009-01-01 16:44:54]: > On Thu, 1 Jan 2009 17:10:10 -0500 > Chess Griffin wrote: > > > * Wade Grant [2009-01-01 13:16:03]: > > > > > I think that there may be a bug or a problem with the ksmoothdock > > > pkg in the repo when using the update tool. I by no means am any > > > sort of guru....... > > > > > > > Wade, I just committed a fix to SVN. It will be the next update. > > Thanks for the bug report! > > > If there's someone on our end that needs to be addressed, don't just > paper over it though - let us know :-) > I will, but in this case everybody is off the hook but me. :-) -- 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 rworkman at slackbuilds.org Thu Jan 1 22:44:54 2009 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 1 Jan 2009 16:44:54 -0600 Subject: [sbopkg-discuss] Re: [Slackbuilds-users] Sbopkg 0.20.0 Released In-Reply-To: <20090101221010.GA31384@localhost> References: <20090101205319.GA22328@localhost> <20090101221010.GA31384@localhost> Message-ID: <20090101164454.4b14b58a@liberty.rlwhome.lan> On Thu, 1 Jan 2009 17:10:10 -0500 Chess Griffin wrote: > * Wade Grant [2009-01-01 13:16:03]: > > > I think that there may be a bug or a problem with the ksmoothdock > > pkg in the repo when using the update tool. I by no means am any > > sort of guru....... > > > > Wade, I just committed a fix to SVN. It will be the next update. > Thanks for the bug report! If there's someone on our end that needs to be addressed, don't just paper over it though - let us know :-) -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 Jan 1 22:10:10 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 1 Jan 2009 17:10:10 -0500 Subject: [sbopkg-discuss] Re: [Slackbuilds-users] Sbopkg 0.20.0 Released In-Reply-To: References: <20090101205319.GA22328@localhost> Message-ID: <20090101221010.GA31384@localhost> * Wade Grant [2009-01-01 13:16:03]: > I think that there may be a bug or a problem with the ksmoothdock pkg > in the repo when using the update tool. I by no means am any sort of > guru....... > Wade, I just committed a fix to SVN. It will be the next update. Thanks for the bug report! -- 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 Thu Jan 1 21:38:36 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 1 Jan 2009 16:38:36 -0500 Subject: [sbopkg-discuss] Re: [Slackbuilds-users] Sbopkg 0.20.0 Released In-Reply-To: References: <20090101205319.GA22328@localhost> Message-ID: <20090101213836.GA3972@localhost> * Wade Grant [2009-01-01 13:16:03]: > Nice tool Chess, this is the first time I have tried it out. > > I think that there may be a bug or a problem with the ksmoothdock pkg > in the repo when using the update tool. I by no means am any sort of > guru....... > > I ran the update tool once and updated my vobcopy and ksmoothdock. > After building them and installing those two pkgs, I ran the update > tool again for the hell of it. > > It once again listed that there was a potential update for > ksmoothdock, here is the message I was presented with: > ---------------------- > ksmoothdock: > POTENTIAL UPDATE > Installed version: ksmoothdock-4.5-i486-1 > Repo Version: ksmoothdock-4.5_${VERSION-i486-1 > > Potential update list complete. > ---------------------- > Thanks, Wade, I'll look into fixing this. Sometimes there are funky issues with specific packages in the repo and this might be one of them. Cheers! -- 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 Thu Jan 1 20:53:19 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 1 Jan 2009 15:53:19 -0500 Subject: [sbopkg-discuss] Sbopkg 0.20.0 Released Message-ID: <20090101205319.GA22328@localhost> Happy New Year! A new version 0.20.0 of sbopkg has been released with /lots/ of updates, new features, and bug fixes -- hence the version jump. :-) Ordinarily, there about 10-15 SVN commits between releases. This time there were close to 50. I think this is an update that most sbopkg users will want to have. I had lots of great user feedback, patches, and suggestions, which I greatly appreciate. I would especially like to thank Erik Hanson and Mauro Giachero for their patches, testing, and suggestions. NOTE: There are three changes to the sbopkg.conf file that will be required before this new version will run, which are discussed below. Here are some of the new features and bug fixes in this latest release of sbopkg. New features: * There is a new -i command line switch which allows the user to build and install packages in a manner similar to the current -b switch for building only. As with the -b switch, the user can build and install more than one package by listing them in quotes. And, by carefully listing dependencies in the right order, it might be possible to build and install dependencies and the final, target package in one go, like this: # sbopkg -i "imlib2 giblib feh" In this case, imlib2 must be built and installed before giblib, both of which need to be built and installed before feh. Given the nature of building dependencies, this may not always work, but it still may be helpful and useful in many cases. * Coupled with the new -i switch, there is a new 'build queue' in the dialog interface. The user can add packages to the queue and then, when ready, can process the queue in the order the packages are listed. The user can choose to build only or build and install the packages in the queue. Again, by listing dependencies in the right order, it may be possible to build dependencies and the final, target package in one go like the feh example above. * After checking for updates, the user is offered the opportunity to add those flagged updates to the build queue automatically. * When building packages individually outside of the build queue, the user is offered the opportunity to build or build and install the package. * There is a new -u command line switch, and a corresponding new dialog menu selection, that allows the user to check if there is an update to sbopkg itself. * A new $DEBUG variable is introduced to the sbopkg.conf file that allow for easier debugging and update list bug reporting. See the sbopkg.conf man page for more detail. Bug Fixes: * Fix issues with the "Installed:/Not Installed" text at the top of info item menu screen. Thanks to Erik Hanson and Mauro Giachero for assistance with this issue. * Improve the wording and button labeling of several dialogs; thanks to Erik Hanson for a patch to implement several of these improvements and thanks to The-Croupier for suggestions on another. * Clean up the customization menu. * Fix issue with typhoon_2001 not building correctly; thanks to cotterochan for the bug report. * Fix django download issue due to their weird tarball naming scheme; thanks to David Somero for the bug report. * Fix mplayer update issue; thanks to all the folks that reported this one. Clearly, mlayer is a popular app. :-) * Fix acroread update issue; thanks to Erik Hanson for the bug report. * Fix build queue failure issue found in 0.20.0rc1 due to not recovering from control-c cleanly; thanks to Mauro Giachero for the bug report. * Fix issue found in 0.20.0rc1 where packages could be added to queue more than once which caused some funky behavior; thanks to Mauro Giachero for the bug report. * Fix issue found in 0.20.0rc1 where customized SlackBuilds were not being used in the build process; thanks to Mauro Giachero for the bug report. * Fix issue foundi n 0.20.0rc1 where the queue processing would even after removing all packages from the queue; thanks to Mauro Giachero for the bug report. Changes to sbopkg.conf: As a result of some of these new features, users are advised of three changes to the sbopkg.conf file. Users can either manually update their existing sbopkg.conf file or use the sbopkg.conf.new file that is installed when you upgrade sbopkg. sbopkg.conf change 1: $OUTPUT is now required. This was commented out in prior versions of sbopkg.conf. The default setting of $OUTPUT is: export OUTPUT=${OUTPUT:-/tmp} this is the same default setting in SBo SlackBuild scripts themselves. sbopkg.conf change 2: $TERMBUILD is deprecated. All building and installing switches now out of dialog and occurs in a terminal in all cases. Having the build take place inside the dialog interface caused some issues and made it difficult to implement some of the new features. So, it went. As a result, you can delete $TERMBUILD from your sbopkg.conf file. sbopkg.conf change 3: As mentioned above, $DEBUG is a new required variable in the sbopkg.conf file. The default setting is DEBUG=0. As always, a sbopkg.conf.new file is installed when upgrading which has these changes in place. Please review this sbopkg.conf.new file and manually merge it with your current sbopkg.conf. 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 irc.freenode.net. A noarch package and source tarball for version 0.20.0 can be found at the sbopkg project website: http://www.sbopkg.org Thanks again to all the folks who sent me bug reports, patches, suggestions, and notes of successes or failures. I want this utility to be useful to the Slackware and SlackBuilds.org community so please keep that feedback coming. Enjoy! -- 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 Thu Jan 8 22:08:05 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 8 Jan 2009 17:08:05 -0500 Subject: [sbopkg-discuss] SVN Updates Message-ID: <20090108220804.GA27203@localhost> There are some nice updates in SVN thanks to two patches from Mauro Giachero in case anyone wants to help test. First, the user can now reverse the order of the items listed in the build queue, which can make it easier when filling up the queue with deps since normally one would find the desired final target package first, add it to the queue, and then start adding in the deps one by one. Before, this would end up with a queue with the packages listed in a backwards order. This list can now be easily reversed. The second new feature of the build queue is that the user can now resort the queue into any order they wish by moving individual items up or down, so if one random package gets inserted out of place, the user can move it up or down in the queue before processing. If you would like to help test these updates, along with some bug fixes and other improvements, please pull from SVN and you can simply run the sbopkg script in the local repo that you pulled down -- no need for a package. See http://sbopkg.org/devel.php for more information on the SVN repo. 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 Wed Jan 14 20:07:52 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Wed, 14 Jan 2009 15:07:52 -0500 Subject: [sbopkg-discuss] Re: Suggestion In-Reply-To: <20090114172650.GA6982@localhost> References: <20090114110721.28048789@liberty.rlwhome.lan> <20090114172650.GA6982@localhost> Message-ID: <20090114200752.GA8821@localhost> * Chess Griffin [2009-01-14 12:26:50]: > Currently, sbopkg can already check to see if there is a new released > package for itself by checking http://sbopkg.org/version.php. I plan > to expand this to have sbopkg pull down the latest package listed in > http://sbopkg.org/pkg.php and update itself. > Okay, I just committed some code to SVN that will check for an update and, optionally, download the new sbopkg package and save it in the $OUTPUT directory. I am a bit nervous about running 'upgradepkg --reinstall --install-new' on the new package while sbopkg is itself running and issuing that command, so the actual upgrade is left to the user to do manually. But, I think this will make it easier and quicker for folks to get the latest package who may not be checking the sbopkg or SBo mailing lists. A new version of sbopkg will be out very soon with this and many other fixes and enhancements. Stay tuned! -- 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 Wed Jan 14 17:26:50 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Wed, 14 Jan 2009 12:26:50 -0500 Subject: [sbopkg-discuss] Re: Suggestion In-Reply-To: <20090114110721.28048789@liberty.rlwhome.lan> References: <20090114110721.28048789@liberty.rlwhome.lan> Message-ID: <20090114172650.GA6982@localhost> * Robby Workman [2009-01-14 11:07:21]: > On Wed, 14 Jan 2009 08:54:23 -0800 (PST) > samac wrote: > > > I was looking at the svn page and saw that there was a slackbuild for > > sbopkg, would it be possible to add sbopkg.slackbuild to the > > slackbuilds site so that sbopkg could update itself? > > > I don't see why it wouldn't be better to just have sbopkg use its own > site to pull the latest build script from there and then offer to > update itself; that way, there's no delay waiting on *us* to push the > newest version to our site. > > You could even have sbopkg rsync itself to the /home/sbo or wherever, > and then put an "--exclude sbopkg/" into the rsync function that > pulls latest SlackBuilds.org site content. > Currently, sbopkg can already check to see if there is a new released package for itself by checking http://sbopkg.org/version.php. I plan to expand this to have sbopkg pull down the latest package listed in http://sbopkg.org/pkg.php and update itself. Also, don't forget that it's easy to run sbopkg from SVN. Just pull down the SVN tree and navigate into the tree to the sbopkg script and run it from there. -- 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 rworkman at slackbuilds.org Wed Jan 14 17:07:21 2009 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 14 Jan 2009 11:07:21 -0600 Subject: [sbopkg-discuss] Re: Suggestion In-Reply-To: References: Message-ID: <20090114110721.28048789@liberty.rlwhome.lan> On Wed, 14 Jan 2009 08:54:23 -0800 (PST) samac wrote: > I was looking at the svn page and saw that there was a slackbuild for > sbopkg, would it be possible to add sbopkg.slackbuild to the > slackbuilds site so that sbopkg could update itself? I don't see why it wouldn't be better to just have sbopkg use its own site to pull the latest build script from there and then offer to update itself; that way, there's no delay waiting on *us* to push the newest version to our site. You could even have sbopkg rsync itself to the /home/sbo or wherever, and then put an "--exclude sbopkg/" into the rsync function that pulls latest SlackBuilds.org site content. -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 Wed Jan 14 16:54:23 2009 From: cotterochan at googlemail.com (samac) Date: Wed, 14 Jan 2009 08:54:23 -0800 (PST) Subject: [sbopkg-discuss] Suggestion Message-ID: I was looking at the svn page and saw that there was a slackbuild for sbopkg, would it be possible to add sbopkg.slackbuild to the slackbuilds site so that sbopkg could update itself? --~--~---------~--~----~------------~-------~--~----~ 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 Jan 15 22:40:19 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 15 Jan 2009 17:40:19 -0500 Subject: [sbopkg-discuss] Re: Sbopkg 0.25.0rc1 In-Reply-To: <54774ad6-7980-402d-b7b8-4f139c94a33c@j39g2000yqn.googlegroups.com> References: <20090115214542.GA18995@localhost> <54774ad6-7980-402d-b7b8-4f139c94a33c@j39g2000yqn.googlegroups.com> Message-ID: <20090115224019.GA20005@localhost> * samac [2009-01-15 14:38:13]: > Hi Chess > > Downloaded and installed 0.25.0rc1 and the changes look good. When > running the self update it wants to update 0.25.0rc1 with 0.20.0, I > guess it is something to do with the rc1 bit of the name. > > samac Yep, that's exactly right. It's not a smart updater -- it just checks the version of the latest official release from a file on the sbopkg.org website and offers to download it if it is different than the version you are running. It will work correctly when upgrading between official releases. -- 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 Thu Jan 15 22:38:13 2009 From: cotterochan at googlemail.com (samac) Date: Thu, 15 Jan 2009 14:38:13 -0800 (PST) Subject: [sbopkg-discuss] Re: Sbopkg 0.25.0rc1 In-Reply-To: <20090115214542.GA18995@localhost> References: <20090115214542.GA18995@localhost> Message-ID: <54774ad6-7980-402d-b7b8-4f139c94a33c@j39g2000yqn.googlegroups.com> Hi Chess Downloaded and installed 0.25.0rc1 and the changes look good. When running the self update it wants to update 0.25.0rc1 with 0.20.0, I guess it is something to do with the rc1 bit of the name. samac On Jan 15, 9:45?pm, Chess Griffin wrote: > I have uploaded a package and source tarball for the first release > candidate for sbopkg version 0.25.0. ?I'll save the specifics of the > fixes, improvements, and new features for the release announcement, > but you can always read through the SVN changelog here:http://code.google.com/p/sbopkg/updates/list. > > Anyway, the package and source tarball for 0.25.0rc1 are located on > the download page here: > > http://code.google.com/p/sbopkg/downloads/list > > If you have the time and inclination, please consider testing this > release candidate to help make sure any little issues or niggles are > addressed before the next release. > > Thank you for your help! > > -- > 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 Thu Jan 15 21:45:42 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 15 Jan 2009 16:45:42 -0500 Subject: [sbopkg-discuss] Sbopkg 0.25.0rc1 Message-ID: <20090115214542.GA18995@localhost> I have uploaded a package and source tarball for the first release candidate for sbopkg version 0.25.0. I'll save the specifics of the fixes, improvements, and new features for the release announcement, but you can always read through the SVN changelog here: http://code.google.com/p/sbopkg/updates/list. Anyway, the package and source tarball for 0.25.0rc1 are located on the download page here: http://code.google.com/p/sbopkg/downloads/list If you have the time and inclination, please consider testing this release candidate to help make sure any little issues or niggles are addressed before the next release. Thank you for your help! -- 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 Jan 19 03:16:01 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Sun, 18 Jan 2009 22:16:01 -0500 Subject: [sbopkg-discuss] Re: Sbopkg 0.25.0 released In-Reply-To: References: <20090117030250.GA8611@localhost> Message-ID: <20090119031601.GA310@localhost> * alkos333 [2009-01-18 01:01:55]: > In the queue management dialog, when one of the items is deselected, > it's removed, which to me is somewhat counter-intuitive. What if some > of the dependencies have already been installed and the admin wants to > deselect them? I thought that by deselecting an item in the queue, > the ON flag would be changed to OFF when saved to a file. I think it > would be better if one could temporarily deselect items from the queue > by unchecking them and if they wanted to remove them entirely, they > could just select on the bottom ? For example, take ardour, > boost and libgnomecanvas are some of the numerous dependencies for it, > but I already have them installed. I added them to the queue because > I'd like to save a complete queue to the file for the future use, but > I'd like to exclude certain items the build process because I don't > want to wait for them to compile. Ok, I have thought more about this and I agree that being able to turn items ON/OFF but keep them in the queue is a good idea, and I have a working implementation of this (not committed to SVN though). However, the only 'problem' is the deleting of items, and this is mainly due to the limitations of dialog. As it stands we have 4 buttons on that screen already. Only when you press OK do you get the selected items written to dialog's output. Anyway, the easiest (though maybe not the most efficient) way to do this is have the current view queue screen basically the same, but with the ability to turn individual items ON or OFF. Then, in the separate "Clear Queue" menu entry that already exists, turn this into another checklist where people can delete individual items (by deselecting them) or delete the whole queue. It puts the deleting in a different screen than the 'View' screen, but again, I think this is mainly because we're starting to bump up against the limitations of dialog. -- 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 xma at gnu.org Sun Jan 18 22:47:34 2009 From: xma at gnu.org (Xavier Maillard) Date: Sun, 18 Jan 2009 23:47:34 +0100 Subject: [sbopkg-discuss] Re: Sbopkg 0.25.0 released In-Reply-To: (alkos's message of "Sun, 18 Jan 2009 01:01:55 -0800 (PST)") References: <20090117030250.GA8611@localhost> Message-ID: <87r6305j09.fsf@gnu.org> alkos333 writes: > Also, may I suggest using ADD and SKP keys (just like in Slackware tag > files) just in case somebody decides to somehow manipulate the saved > queues to combine tagfiles or something. Who knows... I would be more than happy to see this implemented as well ! Great work for this release. Xavier --~--~---------~--~----~------------~-------~--~----~ 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 Jan 18 18:49:53 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Sun, 18 Jan 2009 13:49:53 -0500 Subject: [sbopkg-discuss] Re: Sbopkg 0.25.0 released In-Reply-To: References: <20090117030250.GA8611@localhost> Message-ID: <20090118184951.GA2890@localhost> * alkos333 [2009-01-18 01:01:55]: > > Very nice fixes and additions. Thank you for your time and effort. I > do have a few suggestions and will be more than happy to help > implementing them if we come to consensus. > Thanks! > In the queue management dialog, when one of the items is deselected, > it's removed, which to me is somewhat counter-intuitive. What if some > of the dependencies have already been installed and the admin wants to > deselect them? I thought that by deselecting an item in the queue, > the ON flag would be changed to OFF when saved to a file. I think it > would be better if one could temporarily deselect items from the queue > by unchecking them and if they wanted to remove them entirely, they > could just select on the bottom ? For example, take ardour, > boost and libgnomecanvas are some of the numerous dependencies for it, > but I already have them installed. I added them to the queue because > I'd like to save a complete queue to the file for the future use, but > I'd like to exclude certain items the build process because I don't > want to wait for them to compile. > Well, these are sort of two separate issues -- I can see where you may want to deselect an item but keep it in the queue, and I'll look into add that. However, you can always deselect (which removes) an item from the queue when building to avoid deps you already have installed. Using your ardour example, you could create a queue with all the deps included and save it. Then, later on, you could load that queue from the file, then when start the 'process queue' just deselect those items you already have installed. You would still have the saved file for ardour and all its deps for future use. But, it might be good to keep items in the queue, just turn the dialog setting from ON to OFF, and then when processing the queue, only process those items set to ON. > Also, may I suggest using ADD and SKP keys (just like in Slackware tag > files) just in case somebody decides to somehow manipulate the saved > queues to combine tagfiles or something. Who knows... > Hmm... I'll need to think about this one. This might be something to add at some point in the future. Thanks for the input! -- 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 alkos333 at gmail.com Sun Jan 18 09:01:55 2009 From: alkos333 at gmail.com (alkos333) Date: Sun, 18 Jan 2009 01:01:55 -0800 (PST) Subject: [sbopkg-discuss] Re: Sbopkg 0.25.0 released In-Reply-To: <20090117030250.GA8611@localhost> References: <20090117030250.GA8611@localhost> Message-ID: Very nice fixes and additions. Thank you for your time and effort. I do have a few suggestions and will be more than happy to help implementing them if we come to consensus. In the queue management dialog, when one of the items is deselected, it's removed, which to me is somewhat counter-intuitive. What if some of the dependencies have already been installed and the admin wants to deselect them? I thought that by deselecting an item in the queue, the ON flag would be changed to OFF when saved to a file. I think it would be better if one could temporarily deselect items from the queue by unchecking them and if they wanted to remove them entirely, they could just select on the bottom ? For example, take ardour, boost and libgnomecanvas are some of the numerous dependencies for it, but I already have them installed. I added them to the queue because I'd like to save a complete queue to the file for the future use, but I'd like to exclude certain items the build process because I don't want to wait for them to compile. Also, may I suggest using ADD and SKP keys (just like in Slackware tag files) just in case somebody decides to somehow manipulate the saved queues to combine tagfiles or something. Who knows... On Jan 16, 9:02?pm, Chess Griffin wrote: > A new version 0.25.0 of sbopkg has been released. ?This release > contains many important bug-fixes over 0.20.0, please some nifty new > features, mostly associated with the new build queue, that I think > folks will find helpful. ?Thanks again to everyone who contributed to > this release, including slakmagik, SpacePlod, and others. ?I would > like to give a special shout-out to Mauro Giachero for his numerous > patches and suggestions. ?Many of the improvements to the build queue > were due to Mauro's contributions. > > The build queue, incidentally, has been working extremely well for > myself and for folks using SVN and the 0.25.0 release candidate, and > the feedback I received has helped to greatly improve the build queue > feature over the 0.20.0 release. ?Thanks to everyone who tested and > provided that feedback. > > As you can tell. this is another version jump due to the number of > fixes, enhancements, and new features. ?Here are a few: > > ? * Fix issue where packages were sometimes incorrectly identified as > ? ? already being in the build queue when they were not; thanks to > ? ? SpacePlod for the bug report and thanks to Mauro Giachero for > ? ? further bug reporting and providing a patch to fix it. > ? * Add ability to pass build options/flavors/arguments to the > ? ? SlackBuild when using the dialog interface. > ? * Include ability to reverse or manually sort the items in the build > ? ? queue; thanks to Mauro Giachero for the patches to implement these > ? ? features. > ? * Move all the queue functions into a separate 'Manage Queue' > ? ? submenu off the main menu. > ? * Allow user to save (and load) the build queue between sessions by > ? ? specifing a file and location, so multiple saved queues can be > ? ? maintained. > ? * Automatically backup the current queue upon exiting and offer to > ? ? reload upon first entering the queue submenu. > ? * Provide a menu entry to clear the build queue. > ? * Merge in several patches from Mauro Giachero to display the SVN > ? ? version number; clean up use of cancel/back and ESC (ESC now takes > ? ? you back a step in most dialogs); improve the cleanup process; and > ? ? improve the new build flavors/options dialog. > ? * Apply several patches from slakmagik for various little fixes, > ? ? cleanups, and tweaks. > ? * Create a new 'Utilities' submenu off the main menu and move some > ? ? of the less-important items there in order to clean up the main > ? ? menu. ?It was getting a bit bulky. ?:-) > ? * Add ability to download a new sbopkg package when there is an > ? ? update. > ? * Include optional use of a ~/.sbopkg.conf, which will override > ? ? settings in the system /etc/sbopkg/sbopkg.conf file. > ? * When changing the Slackware version in the dialog interface, offer > ? ? the user the opportunity to save this change in the new > ? ? ~/.sbopkg.conf file. > > Full ChangeLog.txt can be viewed here: > > http://www.sbopkg.org/files/ChangeLog.txt > > 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.25.0 can be found at > the sbopkg project website: > > http://www.sbopkg.org > > 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 Jan 18 04:51:09 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Sat, 17 Jan 2009 23:51:09 -0500 Subject: [sbopkg-discuss] Re: Sbopkg 0.25.0 released In-Reply-To: References: <20090117030250.GA8611@localhost> Message-ID: <20090118045109.GB5741@localhost> * gmartin [2009-01-17 13:15:09]: > > Great tool! Thanks for the quick turnaround on the feature requests. > > Already installed... > Thanks! Let me know if you spot any issues. -- 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 gregmartin1 at gmail.com Sat Jan 17 18:15:09 2009 From: gregmartin1 at gmail.com (gmartin) Date: Sat, 17 Jan 2009 13:15:09 -0500 Subject: [sbopkg-discuss] Re: Sbopkg 0.25.0 released In-Reply-To: <20090117030250.GA8611@localhost> References: <20090117030250.GA8611@localhost> Message-ID: Great tool! Thanks for the quick turnaround on the feature requests. Already installed... On 1/16/09, Chess Griffin wrote: > A new version 0.25.0 of sbopkg has been released. This release > contains many important bug-fixes over 0.20.0, please some nifty new > features, mostly associated with the new build queue, that I think > folks will find helpful. Thanks again to everyone who contributed to > this release, including slakmagik, SpacePlod, and others. I would > like to give a special shout-out to Mauro Giachero for his numerous > patches and suggestions. Many of the improvements to the build queue > were due to Mauro's contributions. > > The build queue, incidentally, has been working extremely well for > myself and for folks using SVN and the 0.25.0 release candidate, and > the feedback I received has helped to greatly improve the build queue > feature over the 0.20.0 release. Thanks to everyone who tested and > provided that feedback. > > As you can tell. this is another version jump due to the number of > fixes, enhancements, and new features. Here are a few: > > * Fix issue where packages were sometimes incorrectly identified as > already being in the build queue when they were not; thanks to > SpacePlod for the bug report and thanks to Mauro Giachero for > further bug reporting and providing a patch to fix it. > * Add ability to pass build options/flavors/arguments to the > SlackBuild when using the dialog interface. > * Include ability to reverse or manually sort the items in the build > queue; thanks to Mauro Giachero for the patches to implement these > features. > * Move all the queue functions into a separate 'Manage Queue' > submenu off the main menu. > * Allow user to save (and load) the build queue between sessions by > specifing a file and location, so multiple saved queues can be > maintained. > * Automatically backup the current queue upon exiting and offer to > reload upon first entering the queue submenu. > * Provide a menu entry to clear the build queue. > * Merge in several patches from Mauro Giachero to display the SVN > version number; clean up use of cancel/back and ESC (ESC now takes > you back a step in most dialogs); improve the cleanup process; and > improve the new build flavors/options dialog. > * Apply several patches from slakmagik for various little fixes, > cleanups, and tweaks. > * Create a new 'Utilities' submenu off the main menu and move some > of the less-important items there in order to clean up the main > menu. It was getting a bit bulky. :-) > * Add ability to download a new sbopkg package when there is an > update. > * Include optional use of a ~/.sbopkg.conf, which will override > settings in the system /etc/sbopkg/sbopkg.conf file. > * When changing the Slackware version in the dialog interface, offer > the user the opportunity to save this change in the new > ~/.sbopkg.conf file. > > Full ChangeLog.txt can be viewed here: > > http://www.sbopkg.org/files/ChangeLog.txt > > 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.25.0 can be found at > the sbopkg project website: > > http://www.sbopkg.org > > Thanks! > > -- > Chess Griffin > -- Sent from my mobile device --~--~---------~--~----~------------~-------~--~----~ 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 Sat Jan 17 03:02:51 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Fri, 16 Jan 2009 22:02:51 -0500 Subject: [sbopkg-discuss] Sbopkg 0.25.0 released Message-ID: <20090117030250.GA8611@localhost> A new version 0.25.0 of sbopkg has been released. This release contains many important bug-fixes over 0.20.0, please some nifty new features, mostly associated with the new build queue, that I think folks will find helpful. Thanks again to everyone who contributed to this release, including slakmagik, SpacePlod, and others. I would like to give a special shout-out to Mauro Giachero for his numerous patches and suggestions. Many of the improvements to the build queue were due to Mauro's contributions. The build queue, incidentally, has been working extremely well for myself and for folks using SVN and the 0.25.0 release candidate, and the feedback I received has helped to greatly improve the build queue feature over the 0.20.0 release. Thanks to everyone who tested and provided that feedback. As you can tell. this is another version jump due to the number of fixes, enhancements, and new features. Here are a few: * Fix issue where packages were sometimes incorrectly identified as already being in the build queue when they were not; thanks to SpacePlod for the bug report and thanks to Mauro Giachero for further bug reporting and providing a patch to fix it. * Add ability to pass build options/flavors/arguments to the SlackBuild when using the dialog interface. * Include ability to reverse or manually sort the items in the build queue; thanks to Mauro Giachero for the patches to implement these features. * Move all the queue functions into a separate 'Manage Queue' submenu off the main menu. * Allow user to save (and load) the build queue between sessions by specifing a file and location, so multiple saved queues can be maintained. * Automatically backup the current queue upon exiting and offer to reload upon first entering the queue submenu. * Provide a menu entry to clear the build queue. * Merge in several patches from Mauro Giachero to display the SVN version number; clean up use of cancel/back and ESC (ESC now takes you back a step in most dialogs); improve the cleanup process; and improve the new build flavors/options dialog. * Apply several patches from slakmagik for various little fixes, cleanups, and tweaks. * Create a new 'Utilities' submenu off the main menu and move some of the less-important items there in order to clean up the main menu. It was getting a bit bulky. :-) * Add ability to download a new sbopkg package when there is an update. * Include optional use of a ~/.sbopkg.conf, which will override settings in the system /etc/sbopkg/sbopkg.conf file. * When changing the Slackware version in the dialog interface, offer the user the opportunity to save this change in the new ~/.sbopkg.conf file. Full ChangeLog.txt can be viewed here: http://www.sbopkg.org/files/ChangeLog.txt 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.25.0 can be found at the sbopkg project website: http://www.sbopkg.org 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 alkos333 at gmail.com Mon Jan 19 17:49:42 2009 From: alkos333 at gmail.com (alkos333) Date: Mon, 19 Jan 2009 09:49:42 -0800 (PST) Subject: [sbopkg-discuss] Re: Question with -current In-Reply-To: <87mydo5iwq.fsf@gnu.org> References: <87mydo5iwq.fsf@gnu.org> Message-ID: <9ac29fab-1d81-4dbc-8974-042eb28bd027@r15g2000prd.googlegroups.com> sbopkg is a tool for SlackBuilds.org and the website doesn't accept SlackBuilds for -current, only stable releases. You could always grab a SlackBuild from the latest repo and try to compile it on -current. After all, that's what's done when preparing the repo for a new release. On Jan 18, 4:49?pm, Xavier Maillard wrote: > Hi, > > This is not entirely a question for sbopkg, if so, please tell me > where to ask it. > > Say I want to use slackware-current, what setting should I use > with sbopkg (and thus with SBo packages) ? 12.2 ? > > Thank you. > > Xavier --~--~---------~--~----~------------~-------~--~----~ 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 xma at gnu.org Sun Jan 18 22:49:41 2009 From: xma at gnu.org (Xavier Maillard) Date: Sun, 18 Jan 2009 23:49:41 +0100 Subject: [sbopkg-discuss] Question with -current Message-ID: <87mydo5iwq.fsf@gnu.org> Hi, This is not entirely a question for sbopkg, if so, please tell me where to ask it. Say I want to use slackware-current, what setting should I use with sbopkg (and thus with SBo packages) ? 12.2 ? Thank you. Xavier --~--~---------~--~----~------------~-------~--~----~ 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 mauro.giachero at gmail.com Wed Jan 21 08:54:40 2009 From: mauro.giachero at gmail.com (mauro_g) Date: Wed, 21 Jan 2009 00:54:40 -0800 (PST) Subject: [sbopkg-discuss] Re: New addition In-Reply-To: <20090120222352.GA9813@localhost> References: <20090120222352.GA9813@localhost> Message-ID: I'd like to take this chance to greet everybody on this list and to thank Chess for the trust he demonstrated adding me to the sbopkg developers group. I've just verified that I can commit (and that "that git-svn stuff" really works), so I'll do my best to overuse my uncensored write access to commit just about any hack I can think of. :-) Nice to meet you all! Mauro Giachero --~--~---------~--~----~------------~-------~--~----~ 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 Tue Jan 20 22:23:52 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Tue, 20 Jan 2009 17:23:52 -0500 Subject: [sbopkg-discuss] New addition Message-ID: <20090120222352.GA9813@localhost> I would like announce that Mauro Giachero has graciously agreed to join me as a developer and help me maintain and improve sbopkg. Mauro has already contributed several important functional improvements and his new update code (which should eliminate the issues previously seen with the update feature) will likely appear in the next release. I really appreciate his help and think sbopkg will be better with him spending more time actively mucking around in the code. :-) Welcome, Mauro! -- 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 Wed Jan 21 14:20:15 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Wed, 21 Jan 2009 09:20:15 -0500 Subject: [sbopkg-discuss] Re: SVN updates -- testing needed In-Reply-To: <20090121075823.5be2bc30@liberty.rlwhome.lan> References: <20090121012332.GA13554@localhost> <20090121075823.5be2bc30@liberty.rlwhome.lan> Message-ID: <20090121142015.GA4373@localhost> * Robby Workman [2009-01-21 07:58:23]: > Hrm... are there any others that we need to rename? I suppose it > would be best to get this out of the way as soon as possible since > you're using a flat text file for this (not that I have a better way, > but a flat text file doesn't scale too well). > > We'll have to keep this in mind for future updates; IOW, let's get the > names right the first time :) > There have not been many renames, but these are the ones I have come across so far (SBo has already changed these, so this file is there to keep up with such changes for updatelist purposes): libsigcxx -> libsigc++ libxmlxx -> libxml++ TiMidityxx -> TiMidity++ MPlayer -> mplayer There was also an issue with artwiz-aleczapka but I cannot recall exactly what it was. -- 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 rworkman at slackbuilds.org Wed Jan 21 13:58:23 2009 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 21 Jan 2009 07:58:23 -0600 Subject: [sbopkg-discuss] Re: SVN updates -- testing needed In-Reply-To: <20090121012332.GA13554@localhost> References: <20090121012332.GA13554@localhost> Message-ID: <20090121075823.5be2bc30@liberty.rlwhome.lan> On Tue, 20 Jan 2009 20:23:32 -0500 Chess Griffin wrote: > Finally, and probably most importantly, Mauro's new update code has > been merged in, so heavy testing of the update feature would be > greatly appreciated. This _should_ eliminate the need for any of the > application-specific hacks. This code requires a new file to handle > some application name changes, such as libxmlxx to libxml++. This > file goes in /etc/sbopkg and will automatically be installed with the > next release's package. However, you'll need it now if you are going > to test from SVN. You can grab this file from SVN: > > http://sbopkg.googlecode.com/svn/trunk/src/etc/sbopkg/sbopkg-renames Hrm... are there any others that we need to rename? I suppose it would be best to get this out of the way as soon as possible since you're using a flat text file for this (not that I have a better way, but a flat text file doesn't scale too well). We'll have to keep this in mind for future updates; IOW, let's get the names right the first time :) -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 Wed Jan 21 01:23:32 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Tue, 20 Jan 2009 20:23:32 -0500 Subject: [sbopkg-discuss] SVN updates -- testing needed Message-ID: <20090121012332.GA13554@localhost> A few new changes and feature requests have been added in to SVN and they need some testing: The first involves the request that unselected items in the queue are retained and not deleted. This is now working in SVN -- the delete part has been moved to a separate menu entry in the queue submenu. That handles deleting individual items or deleting the entire queue. But, you can now unselect individual items in the view queue and they will be kept, only turned OFF. When processing the queue, only the items turned ON will be built/installed. Additionally, how items are added to the queue has undergone a fair amount of revision. This is to allow for the fact that items may be in the queue but the user may want to overwrite them (i.e. when there is an update), or when loading a user's saved queue into a queue that may have a duplicate entry etc. Anyway, I would greatly appreciate lots of testing of the build queue -- adding, removing, saving, loading etc. Another change requires a new sbopkg.conf variable, the default which will be as follows: LOGFILE=$TMP/sbopkg-build-log This is the default location of the permanent build log, which means it can now be set manually. If you test from SVN, please add this to your sbopkg.conf file. Finally, and probably most importantly, Mauro's new update code has been merged in, so heavy testing of the update feature would be greatly appreciated. This _should_ eliminate the need for any of the application-specific hacks. This code requires a new file to handle some application name changes, such as libxmlxx to libxml++. This file goes in /etc/sbopkg and will automatically be installed with the next release's package. However, you'll need it now if you are going to test from SVN. You can grab this file from SVN: http://sbopkg.googlecode.com/svn/trunk/src/etc/sbopkg/sbopkg-renames 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 Sat Jan 24 14:18:22 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Sat, 24 Jan 2009 09:18:22 -0500 Subject: [sbopkg-discuss] Helper script to test from SVN Message-ID: <20090124141821.GA18802@localhost> Hello folks -- there are lots of good improvements going into the sbopkg SVN repository these days. Many thanks to Mauro Giachero and slakmagik for the assistance. From time to time, folks have asked about how to use the SVN repository to help test. One way is to pull down the SVN repo based on the instructions on the sbopkg googlecode page and run it from within the directory. Now, there is an easier way. Slakmagik has contributed a little script that I have added to the /tools directory in the sbopkg SVN repo. This script will do any combination of the following: sync a copy of the sbopkg SVN mirror; build a package from the SVN repo; or install the package built from the SVN repo. It's a pretty nifty script and works well. You can download a copy directly from here: http://sbopkg.googlecode.com/svn/trunk/tools/sspm Just save this file, make it executable, create a directory that you want to hold the sbopkg SVN repo, edit the user-modifiable variables in the sspm script and then run it with the -h to see the cli options. Thanks to slakmagik for making this script available! And if anyone wanted to use this to help test what's going on in SVN, I would /greatly/ appreciate it. We have lots of good improvements going on and I'd really like to get some more feedback before the next release. 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 bkirkp at gmail.com Mon Jan 26 21:26:17 2009 From: bkirkp at gmail.com (T2F) Date: Mon, 26 Jan 2009 13:26:17 -0800 (PST) Subject: [sbopkg-discuss] Re: sbopkg 0.25 Problems In-Reply-To: <20090126201638.GA28444@localhost> References: <8970aba3-54e8-41f5-9092-2a00bb45ce1d@w39g2000prb.googlegroups.com> <20090126201638.GA28444@localhost> Message-ID: On Jan 26, 2:16?pm, Chess Griffin wrote: > The 'workaround' here is to do what sbopkg allows you to do already: > modify the .info file. > > Let me know if any of this doesn't make any sense. ?:-) > > Chess Griffin It makes plenty of sense, & won't be a problem. I should have realized that the ".info" file was involved when I saw the md5sum for the original version in the log. On Mon, 26 Jan 2009 01:50 pm, Robby Workman wrote: > Aha. Now I know who you are :-) > Interesting how often LQ/IRC nicks don't get properly linked to real > names in my head... Hi, Robby. Yeah, I'm one of those who hides behind an alias. I have been K5TTF since I passed my Novice Amateur Radio exam in 1958, & have been called TSquaredF by various hams ever since. Regards, Billo --~--~---------~--~----~------------~-------~--~----~ 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 Jan 26 20:16:38 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Mon, 26 Jan 2009 15:16:38 -0500 Subject: [sbopkg-discuss] Re: sbopkg 0.25 Problems In-Reply-To: <8970aba3-54e8-41f5-9092-2a00bb45ce1d@w39g2000prb.googlegroups.com> References: <8970aba3-54e8-41f5-9092-2a00bb45ce1d@w39g2000prb.googlegroups.com> Message-ID: <20090126201638.GA28444@localhost> * T2F [2009-01-26 10:41:12]: > My second problem also involved building ffmpeg. I wanted to buiild > ffmpeg with the most recent updates. There are instructions for doing > that in the ffmpeg README/SlackBuild. I followed those instructions & > put ffmpeg-20090121... in .../sbo/src. I set the above options, then > selected "Build". I selected "Build" from the Build/Build&Install > dialog box. I then got a "Use Options" dialog box & selected "yes". I > then got the following errors: > > Building ffmpeg > Checking MD5SUM for ffmpeg-20081105.tar.bz2... > OK > Building Slackware package for ffmpeg... > tar: /mnt/hal/slack/sbo/12.2/multimedia/ffmpeg/ > ffmpeg-20090121.tar.bz2: Cannot open: No such file or directory > tar: Error is not recoverable: exiting now > This actually presents a couple of problems. Sbopkg parses the .info file for the Download link and the MD5SUM. If the source is already in the SRCDIR, then it won't try to download again, but it still has to look to the .info file to figure out what the source tarball is called. In this case, the source tarball is ffmpeg-20081105.tar.bz2. On top of that, the MD5SUM in the .info file is the MD5SUM for the 20081105 tarball. You can probably see how the error occurred. The 'workaround' here is to do what sbopkg allows you to do already: modify the .info file. This feature is there for exactly this reason. Just go into the 'Custom' menu the ffmpeg menu, and edit a local .info file. Replace VERSION= with VERSION=20090121, make a similar change of date to the DOWNLOAD link, and also change the MD5SUM to the md5 of the new 2009 tarball. Let me know if any of this doesn't make any sense. :-) -- 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 rworkman at slackbuilds.org Mon Jan 26 19:50:59 2009 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 26 Jan 2009 13:50:59 -0600 Subject: [sbopkg-discuss] Re: sbopkg 0.25 Problems In-Reply-To: <8970aba3-54e8-41f5-9092-2a00bb45ce1d@w39g2000prb.googlegroups.com> References: <8970aba3-54e8-41f5-9092-2a00bb45ce1d@w39g2000prb.googlegroups.com> Message-ID: <20090126135059.3d1a2242@liberty.rlwhome.lan> On Mon, 26 Jan 2009 10:41:12 -0800 (PST) T2F wrote: > ... > Regards, > Bill Kirkpatrick > "TSquaredF" on LQ Aha. Now I know who you are :-) Interesting how often LQ/IRC nicks don't get properly linked to real names in my head... -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 Mon Jan 26 19:27:20 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Mon, 26 Jan 2009 14:27:20 -0500 Subject: [sbopkg-discuss] Re: sbopkg 0.25 Problems In-Reply-To: <8970aba3-54e8-41f5-9092-2a00bb45ce1d@w39g2000prb.googlegroups.com> References: <8970aba3-54e8-41f5-9092-2a00bb45ce1d@w39g2000prb.googlegroups.com> Message-ID: <20090126192720.GA27108@localhost> * T2F [2009-01-26 10:41:12]: > > I have a couple of bumps in my sbopkg road. Nothing of any major > importance, but I thought I should make them public. > Excellent - bug reports are a good thing. :-) > First, I have been very happy with sbopkg, haven't used the build > queue yet, but I do like the ability to pass options to the build > script. I have found a problem with that though. > > I was building ffmpeg, having typed the options: > > AMRNB=yes AMRWB=yes VERSION=20090121 > > But I made a typo, and wanted to go back & edit them. However, I could > not do it. The window would flash & then go back to the menu for > ffmpeg when I selected the "Options" menu item. I had to delete the > options.sbopkg file, then recreate it with the "Options" menu item. Ah, yes, I can reproduce this and just fixed it. Will commit this fix to SVN and it will be in the next release. Thanks! > > My second problem also involved building ffmpeg. I wanted to buiild > ffmpeg with the most recent updates. There are instructions for doing > that in the ffmpeg README/SlackBuild. I followed those instructions & > put ffmpeg-20090121... in .../sbo/src. I set the above options, then > selected "Build". I selected "Build" from the Build/Build&Install > dialog box. I then got a "Use Options" dialog box & selected "yes". I > then got the following errors: > > Building ffmpeg > Checking MD5SUM for ffmpeg-20081105.tar.bz2... > OK > Building Slackware package for ffmpeg... > tar: /mnt/hal/slack/sbo/12.2/multimedia/ffmpeg/ > ffmpeg-20090121.tar.bz2: Cannot open: No such file or directory > tar: Error is not recoverable: exiting now > Ah, yes, I can see the issue. I have not started working on a fix, but will do so shortly. I'll report back when it's fixed. Thanks, Bill, for the reports. I really appreciate it. -- 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 bkirkp at gmail.com Mon Jan 26 18:41:12 2009 From: bkirkp at gmail.com (T2F) Date: Mon, 26 Jan 2009 10:41:12 -0800 (PST) Subject: [sbopkg-discuss] sbopkg 0.25 Problems Message-ID: <8970aba3-54e8-41f5-9092-2a00bb45ce1d@w39g2000prb.googlegroups.com> I have a couple of bumps in my sbopkg road. Nothing of any major importance, but I thought I should make them public. First, I have been very happy with sbopkg, haven't used the build queue yet, but I do like the ability to pass options to the build script. I have found a problem with that though. I was building ffmpeg, having typed the options: AMRNB=yes AMRWB=yes VERSION=20090121 But I made a typo, and wanted to go back & edit them. However, I could not do it. The window would flash & then go back to the menu for ffmpeg when I selected the "Options" menu item. I had to delete the options.sbopkg file, then recreate it with the "Options" menu item. My second problem also involved building ffmpeg. I wanted to buiild ffmpeg with the most recent updates. There are instructions for doing that in the ffmpeg README/SlackBuild. I followed those instructions & put ffmpeg-20090121... in .../sbo/src. I set the above options, then selected "Build". I selected "Build" from the Build/Build&Install dialog box. I then got a "Use Options" dialog box & selected "yes". I then got the following errors: Building ffmpeg Checking MD5SUM for ffmpeg-20081105.tar.bz2... OK Building Slackware package for ffmpeg... tar: /mnt/hal/slack/sbo/12.2/multimedia/ffmpeg/ ffmpeg-20090121.tar.bz2: Cannot open: No such file or directory tar: Error is not recoverable: exiting now ****************************************** PACKAGE BUILDING/INSTALLATION SUMMARY LOG Using SlackBuilds.org 12.2 repository ffmpeg: Error occurred with build. Please check the log. ****************************************** Press any key to continue. The only way I could get sbopkg to build this package was to provide a link in $CWD to the new source. Once I did that, the package built fine. I want to crawl through the code to see how these miracles are performed (I am always looking for hints/tips!), but have been involved in a custom rsync script & every time I think I have it right, I find another bug. Oh, well, it helps the time pass. Regards, Bill Kirkpatrick "TSquaredF" on LQ --~--~---------~--~----~------------~-------~--~----~ 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 Jan 29 15:09:51 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 29 Jan 2009 10:09:51 -0500 Subject: [sbopkg-discuss] Sbopkg 0.26.0 released Message-ID: <20090129150951.GA29706@localhost> A new version 0.26.0 of sbopkg has been released. This release would not have been possible without the help of Mauro Giachero and slakmagik. For those who might have missed the announcement on the sbopkg mailing list, Mauro has joined me as co-developer of sbopkg, and will be helping me maintain and improve sbopkg. Additionally, slakmagik has contributed many excellent patches, as well as the very useful 'sspm' script mentioned in the ChangeLog below. The big news in this release is the entirely new update code written by Mauro, which greatly reduces, if not eliminates, the problems and false positives seen previously. A lot of time was also spent on improving the build queue and generally cleaning up the code. Also, please be aware that there is a new file, sbopkg-renames, as well as a new sbopkg.conf configuration variable, LOGFILE, both of which are mentioned below. Here are some of the highlights of the ChangeLog: * Add in new update code by Mauro Giachero. This /greatly/ improves how the updates are handled and virtually eliminates the need for specific application quirks. Please note there is a new file /etc/sbopkg/sbopkg-renames that handles a few name changes. If you upgrade sbopkg with the new package, then this file will be automatically installed. If not, you'll need to grab this file from the source tarball and move it there manually. Many thanks to Mauro for the hard work in finally getting the update code done right. :-) * Change how selecting/unselecting items in the build queue are handled. Now, when items are unselected, they remain in the queue but are turned "OFF" and when the queue is processed, only those packages turned "ON" will be built or installed. * Improve how packages are added to the queue. The user is now prompted if they want to replace items already in the queue or skip them. This may be helpful if a user has saved a queue with lots of dependencies that are then updated through the rsync process. The updates can be added to the queue, replacing the old versions. * Add in a nice progress gauge when running the update list rather than the warning message. Thanks to alkos333 for the idea and initial implementation, and thanks to Mauro Giachero for working on the CLI version. * Replace the 'Clear Queue' menu item with 'Delete Queue Items' which provides the user the ability to delete individual items in the queue or clear the entire build queue. * Add in ability to have a /local directory in the local SBo repository tree on a user's system that is in parallel with other SBo directories (i.e. /home/sbo/local). As long as this directory is maintained in an SBo style (including user-defined categories), then sbopkg will pick them up and the user can change their SLACKVER to 'local' and build/install packages from there. This might be useful in testing pre-submissions to SBo or for maintaining other software not in SBo. This was inspired by a similar idea contributed by slakmagik. Please see the sbopkg.conf(5) man page for more information. * Commit a patch from slakmagik that adds a new sbopkg.conf variable LOGFILE where the user can decide the name and location of the permanent build log, if used; thanks to slakmagik for the patch. * Fix issue where downloaded sources with spaces in their file names would cause an MD5SUM failure; thanks to alkos333 for the bug report, and thanks to Mauro Giachero for improving my initial bug fix implementation. * Commit several other patches from slakmagik that improve the handling of the search box upon search failures; tweak the precheck log a bit; improve the checking of root privilegs, and improve the handling of the directory-creation checks; thanks to slakmagik for these patches. * Add 'sspm' utility script by slakmagik which makes mirroring the sbopkg SVN repository and making a package from the local SVN mirror very easy; this script is located in the /tools directory in the sbopkg SVN repository; thanks to slakmagik for the script. * Fix issue where ARCH would sometimes not get picked up in info_item menu (notably for OpenOffice.org); thanks to artourter for the bug report, and thanks to Mauro for the fix. A full ChangeLog.txt can be viewed here: http://www.sbopkg.org/files/ChangeLog.txt As always, please report any bugs to me via email, the sbopkg mailing list, or, using the Issue Tracker on the projects Google Code website. I can also be found in #sbopkg, #slackbuilds, and ##slackware on freenode. A noarch package and source tarball for version 0.26.0 can be found at the sbopkg project website: http://www.sbopkg.org Thanks again to Mauro and slakmagik and to everyone else who helped test and send in bug reports. Enjoy! -- 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 phillip.c.warner at gmail.com Fri Jan 30 06:41:25 2009 From: phillip.c.warner at gmail.com (Phillip Warner) Date: Fri, 30 Jan 2009 00:41:25 -0600 Subject: [sbopkg-discuss] Re: Feature request - Option to have cache cleared after build In-Reply-To: <20090130035851.GB11406@localhost> References: <20090130035851.GB11406@localhost> Message-ID: On Thu, Jan 29, 2009 at 9:58 PM, Chess Griffin wrote: > > Do you mean have the option to delete the source tarball? If so, then > during a build queue run, would you want to be prompted for this after > each individual package or at the end of the build queue? And would you > want to be able to delete any single one or all of them at once? Just > trying to weigh the benefits since you can currently delete individual > sources by going into that application's menu. > > Thanks for the suggestion. > > -- > Chess Griffin > Chess, Yes, I mean the source tarball. However, I am suggesting a switch/option that can be enabled (say from Utilities) so that any time you build a package (whether queued or not) it is automatically deleted upon a successful build (immediately). This is useful, for instance, if you are low on disk space and you want to queue up some large packages (qt4, openoffice, etc) and let the machine crank for a while. You won't have to worry about disk space filling up as fast since the source tarballs get deleted as you go. It should be noted, however, that this would be most useful if the package-$PRGNAM folder could also be auto-deleted after every successful package build. You could even have the package itself auto-deleted after it is installed via sbopkg. Perhaps an "auto-delete" dialog with three check boxes for each of the options would work best. Thanks for all your work on this program. It certainly is maturing very well. --phillip --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~--- -------------- next part -------------- An HTML attachment was scrubbed... URL: From chess at chessgriffin.com Fri Jan 30 03:58:51 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 29 Jan 2009 22:58:51 -0500 Subject: [sbopkg-discuss] Re: Feature request - Option to have cache cleared after build In-Reply-To: References: Message-ID: <20090130035851.GB11406@localhost> * shadowsnipes [2009-01-29 18:04:42]: > > It would be nice for there to be an option to have cache cleared after > a successful build. I don't mean have the entire cache emptied, but > rather have the specific source just built deleted. > > This would be similar to slackpkg's functionality. Do you mean have the option to delete the source tarball? If so, then during a build queue run, would you want to be prompted for this after each individual package or at the end of the build queue? And would you want to be able to delete any single one or all of them at once? Just trying to weigh the benefits since you can currently delete individual sources by going into that application's menu. Thanks for the suggestion. -- 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 phillip.c.warner at gmail.com Fri Jan 30 02:04:42 2009 From: phillip.c.warner at gmail.com (shadowsnipes) Date: Thu, 29 Jan 2009 18:04:42 -0800 (PST) Subject: [sbopkg-discuss] Feature request - Option to have cache cleared after build Message-ID: It would be nice for there to be an option to have cache cleared after a successful build. I don't mean have the entire cache emptied, but rather have the specific source just built deleted. This would be similar to slackpkg's functionality. --~--~---------~--~----~------------~-------~--~----~ 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 Jan 30 04:39:42 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 29 Jan 2009 23:39:42 -0500 Subject: [sbopkg-discuss] Re: annoying build queue messages from Update dialog In-Reply-To: <20090130040149.GC11406@localhost> References: <18061a2d-ecb0-4f69-bc22-51f6f80f429d@t11g2000yqg.googlegroups.com> <20090130040149.GC11406@localhost> Message-ID: <20090130043941.GI11406@localhost> * Chess Griffin [2009-01-29 23:01:49]: > * shadowsnipes [2009-01-29 18:12:49]: > > > > > When using the Updates dialog tons of SlackBuilds can be added to the > > build queue. This is a great feature, but unfortunately it is > > annoying to have to click OK for every single item added. > > This is now 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 chess at chessgriffin.com Fri Jan 30 04:01:49 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 29 Jan 2009 23:01:49 -0500 Subject: [sbopkg-discuss] Re: annoying build queue messages from Update dialog In-Reply-To: <18061a2d-ecb0-4f69-bc22-51f6f80f429d@t11g2000yqg.googlegroups.com> References: <18061a2d-ecb0-4f69-bc22-51f6f80f429d@t11g2000yqg.googlegroups.com> Message-ID: <20090130040149.GC11406@localhost> * shadowsnipes [2009-01-29 18:12:49]: > > When using the Updates dialog tons of SlackBuilds can be added to the > build queue. This is a great feature, but unfortunately it is > annoying to have to click OK for every single item added. > > Instead of showing a dialog for every item, in your loop you can just > add it to some list in the background. When you get to an item that > you may have to ignore or skip then a dialog can be shown for that. > After all the items are processed, then the entire list of items added > to the build queue can be shown at once. Yes, this will taken care of in the next release. 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 phillip.c.warner at gmail.com Fri Jan 30 02:12:49 2009 From: phillip.c.warner at gmail.com (shadowsnipes) Date: Thu, 29 Jan 2009 18:12:49 -0800 (PST) Subject: [sbopkg-discuss] annoying build queue messages from Update dialog Message-ID: <18061a2d-ecb0-4f69-bc22-51f6f80f429d@t11g2000yqg.googlegroups.com> When using the Updates dialog tons of SlackBuilds can be added to the build queue. This is a great feature, but unfortunately it is annoying to have to click OK for every single item added. Instead of showing a dialog for every item, in your loop you can just add it to some list in the background. When you get to an item that you may have to ignore or skip then a dialog can be shown for that. After all the items are processed, then the entire list of items added to the build queue can be shown at once. --~--~---------~--~----~------------~-------~--~----~ 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 Jan 30 04:14:56 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 29 Jan 2009 23:14:56 -0500 Subject: [sbopkg-discuss] Re: Feature request - view more files In-Reply-To: References: Message-ID: <20090130041456.GG11406@localhost> * shadowsnipes [2009-01-29 18:15:54]: > > In the SlackBuild dialog it would be nice to be able to quickly view a > listing of the SlackBuild directory (like the tree show on the bottom > of SlackBuilds.org pages) and the contents of the doinst.sh (if > available, and not an option otherwise). Something along these lines might be doable. Let me give this one some thought. -- 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 phillip.c.warner at gmail.com Fri Jan 30 02:15:54 2009 From: phillip.c.warner at gmail.com (shadowsnipes) Date: Thu, 29 Jan 2009 18:15:54 -0800 (PST) Subject: [sbopkg-discuss] Feature request - view more files Message-ID: In the SlackBuild dialog it would be nice to be able to quickly view a listing of the SlackBuild directory (like the tree show on the bottom of SlackBuilds.org pages) and the contents of the doinst.sh (if available, and not an option otherwise). --~--~---------~--~----~------------~-------~--~----~ 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 Jan 30 04:08:36 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 29 Jan 2009 23:08:36 -0500 Subject: [sbopkg-discuss] Re: Feature request - show diffs In-Reply-To: References: Message-ID: <20090130040836.GD11406@localhost> * shadowsnipes [2009-01-29 18:24:21]: > > When you choose to build a package a dialog pops up if you have > customized the SlackBuild. You are asked whether or not to use your > custom .SlackBuild file or the official repo file. A good third > option would be to show a diff of the two (and then return back to > that dialog after done viewing). Not a bad idea. I'll put this on the TODO. :-) > > Also, I still think it would be a great option to be able to view of > diff of the changes between the current SlackBuild folders and the > previous versions. One way to do this would be to use rsync's backup > feature and diff against what is in there. If there is no > corresponding SlackBuild folder backed up then no diff would need to > be shown. Of course, the sbo-renames file would have to be used in > case one of the SlackBuilds backed up were renamed in the repo. I'm going to have to think about this one. Thanks again for the great suggestions. -- 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 phillip.c.warner at gmail.com Fri Jan 30 02:24:21 2009 From: phillip.c.warner at gmail.com (shadowsnipes) Date: Thu, 29 Jan 2009 18:24:21 -0800 (PST) Subject: [sbopkg-discuss] Feature request - show diffs Message-ID: When you choose to build a package a dialog pops up if you have customized the SlackBuild. You are asked whether or not to use your custom .SlackBuild file or the official repo file. A good third option would be to show a diff of the two (and then return back to that dialog after done viewing). Also, I still think it would be a great option to be able to view of diff of the changes between the current SlackBuild folders and the previous versions. One way to do this would be to use rsync's backup feature and diff against what is in there. If there is no corresponding SlackBuild folder backed up then no diff would need to be shown. Of course, the sbo-renames file would have to be used in case one of the SlackBuilds backed up were renamed in the repo. --~--~---------~--~----~------------~-------~--~----~ 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 Jan 30 04:12:49 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 29 Jan 2009 23:12:49 -0500 Subject: [sbopkg-discuss] Re: Feature request - test build option In-Reply-To: References: Message-ID: <20090130041249.GE11406@localhost> * shadowsnipes [2009-01-29 18:35:34]: > > It is often a very good idea to test buildscripts as a normal user > before running them as root. This could be added to sbopkg as an > option for root. > > Basically, root would select "test build" instead of "build". > root would then su as another user, > change $TMP and $OUTPUT to a directory that the user can use, > copy the SlackBuild to a temporary directory that the user can write > to, > sed the "chown root:root" in the SlackBuild to comment it out > build the package > exit the su > > All the user configurable vars would need to be checked for the > selected user of course. Heh, I'm going to have to think about this one as well. -- 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 phillip.c.warner at gmail.com Fri Jan 30 02:35:34 2009 From: phillip.c.warner at gmail.com (shadowsnipes) Date: Thu, 29 Jan 2009 18:35:34 -0800 (PST) Subject: [sbopkg-discuss] Feature request - test build option Message-ID: It is often a very good idea to test buildscripts as a normal user before running them as root. This could be added to sbopkg as an option for root. Basically, root would select "test build" instead of "build". root would then su as another user, change $TMP and $OUTPUT to a directory that the user can use, copy the SlackBuild to a temporary directory that the user can write to, sed the "chown root:root" in the SlackBuild to comment it out build the package exit the su All the user configurable vars would need to be checked for the selected user of course. --~--~---------~--~----~------------~-------~--~----~ 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 Jan 30 04:40:40 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 29 Jan 2009 23:40:40 -0500 Subject: [sbopkg-discuss] Re: Suggestion - sbopkg.conf In-Reply-To: <20090130041330.GF11406@localhost> References: <56e4d6dc-f8b2-45fd-b31c-428fdbcd86e0@e22g2000vbe.googlegroups.com> <20090130041330.GF11406@localhost> Message-ID: <20090130044039.GJ11406@localhost> * Chess Griffin [2009-01-29 23:13:30]: > * T2F [2009-01-29 19:18:27]: > > > > > I upgraded to 0.26 today & really appreciate the "local" option. I > > modified the SLACKVER line in sbopkg.conf to: > > > > SLACKVER=${SLACKVER:-12.2} > > > > so that I can start by: > > > > SLACKVER=local sbopkg > > > > & get to the "local" files. Not a big deal, but maybe helpful. > > Regards, > > Bill > > > > Good idea. Yes, I'll make this change. > Done. :-) Thanks for the suggestion! -- 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 Fri Jan 30 04:13:30 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 29 Jan 2009 23:13:30 -0500 Subject: [sbopkg-discuss] Re: Suggestion - sbopkg.conf In-Reply-To: <56e4d6dc-f8b2-45fd-b31c-428fdbcd86e0@e22g2000vbe.googlegroups.com> References: <56e4d6dc-f8b2-45fd-b31c-428fdbcd86e0@e22g2000vbe.googlegroups.com> Message-ID: <20090130041330.GF11406@localhost> * T2F [2009-01-29 19:18:27]: > > I upgraded to 0.26 today & really appreciate the "local" option. I > modified the SLACKVER line in sbopkg.conf to: > > SLACKVER=${SLACKVER:-12.2} > > so that I can start by: > > SLACKVER=local sbopkg > > & get to the "local" files. Not a big deal, but maybe helpful. > Regards, > Bill > Good idea. Yes, I'll make this change. -- 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 bkirkp at gmail.com Fri Jan 30 03:18:27 2009 From: bkirkp at gmail.com (T2F) Date: Thu, 29 Jan 2009 19:18:27 -0800 (PST) Subject: [sbopkg-discuss] Suggestion - sbopkg.conf Message-ID: <56e4d6dc-f8b2-45fd-b31c-428fdbcd86e0@e22g2000vbe.googlegroups.com> I upgraded to 0.26 today & really appreciate the "local" option. I modified the SLACKVER line in sbopkg.conf to: SLACKVER=${SLACKVER:-12.2} so that I can start by: SLACKVER=local sbopkg & get to the "local" files. Not a big deal, but maybe helpful. Regards, Bill --~--~---------~--~----~------------~-------~--~----~ 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 Jan 30 22:20:24 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Fri, 30 Jan 2009 17:20:24 -0500 Subject: [sbopkg-discuss] Sbopkg 0.26.1 released - security update Message-ID: <20090130222023.GA30961@localhost> This is a quick point release updating the latest sbopkg to version 0.26.1 with some important security improvements. Here is the brief ChangeLog: * Implement some security fixes, namely, customize the output of some of the menus so only things that can be done as root (i.e. build, install, process the queue) are seen by the root user; also add a check to make sure only root can install packages and that packages are correctly set with root:root permissions. Thanks to Phillip Warner for the report and suggestions. * Modify SLACKVER in sbopkg.conf so it can be passed at runtime to sbopkg. Thanks to TSquaredF for the suggestion. You may choose to update your SLACKVER based on what is in the sbopkg.conf.new. * Quiet down the number of messages displayed when updated items are added to the queue; thanks to Phillip Warner for the suggestion. * Fix issue where sometimes duplicate items would appear in the search results dialog; thanks to Phillip Warner for the suggestion. An updated source tarball and package are available on the sbopkg web site: http://www.sbopkg.org 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 Sat Jan 31 02:15:50 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Fri, 30 Jan 2009 21:15:50 -0500 Subject: [sbopkg-discuss] Re: regression in 0.26.1 In-Reply-To: <20090131005256.GA32404@localhost> References: <20090131005256.GA32404@localhost> Message-ID: <20090131021550.GA30740@localhost> * Chess Griffin [2009-01-30 19:52:56]: > Sorry folks, but there is a slight regression in 0.26.1 that did not > appear in my testing which prevents packages from being installed. I > apologize. I'll post an update shortly. > Ok, I have uploaded a 0.26.2 package and source tarball that fixes the regression. If you would rather manually patch sbopkg, the diff is below. Again, I apologize for the error. --- sbopkg/trunk/src/usr/bin/sbopkg 2009-01-29 23:34:48.000000000 -0500 +++ ./workingsbopkg 2009-01-30 19:50:24.000000000 -0500 @@ -1697,7 +1697,7 @@ echo "Built package: $NEWPACKAGE" >> $SUMMARYLOG echo "Built package: $NEWPACKAGE" if [ "$INSTALLPKGS" = "1" ]; then - install_package $SRCNAME + install_package $NEWPACKAGE echo "Done installing/upgrading package for $PKG." echo "Installed package: $NEWPACKAGE" >> $SUMMARYLOG fi -- 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 Sat Jan 31 00:52:56 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Fri, 30 Jan 2009 19:52:56 -0500 Subject: [sbopkg-discuss] regression in 0.26.1 Message-ID: <20090131005256.GA32404@localhost> Sorry folks, but there is a slight regression in 0.26.1 that did not appear in my testing which prevents packages from being installed. I apologize. I'll post an update shortly. -- Chess Griffin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: