From slakmagik at gmail.com Thu Apr 28 03:16:36 2011 From: slakmagik at gmail.com (slakmagik) Date: Wed, 27 Apr 2011 23:16:36 -0400 Subject: [sbopkg-users] Sbopkg 0.35.0 Released Message-ID: <20110428031636.GA27640@devbox> Greetings, all. This release includes a few small features, a few modifications, and a few more or less minor bugs. Thanks to everyone who helped. Congrats to Pat, et al., on the new Slackware. sbopkg 0.35.0 (2011-04-28 02:48 UTC) FEATURES * This release of sbopkg is Slackware 13.37-ready. (Congrats to all involved in the Slackware release.) * The READMEs of all installed packages can now be read from the main menu's list/uninstall item. (Selection state will also now be remembered.) Thanks to dmotaleite for the RFE. * Similarly, the -R and -p flags can now be combined to page through the READMEs of all installed packages. * Added ponce's repo (SBo variant for -current) to the default repos. Thanks to Mauro for suggesting this about a year ago. Note that this is unsupported (if a build from this repo breaks in sbopkg you get to keep both pieces) but people seem pleased with this repo and it'll save a step for new users. Note that the default repo files have been reordered, as well. 50-sb64 is now 70, 60-local is now 50, and the new one is 60. This puts the unsupported repos last. If by chance you have a file with those names already in there, upgrading sbopkg will clobber them. See each of the two following sections for more repo-related modifications and bugfixing. * Added a bash completion file for sbopkg. This is independent of the bash-completion package. It can be found in the new doc/contrib directory. Source the file (in your shell startup files if you want it always on automatically) from its current location or wherever you wish to copy it and you should be able to complete some of sbopkg's flags and their arguments. Also see the KNOWN_ISSUES file. Thanks to Sergey V. for this contribution. MODIFICATIONS * Updated French man pages. Thanks to Marie-Claude Collilieux. * Revised documentation: moved the queuefiles directory into a new contrib directory, renamed the README-*.d documents, stripping the '.d'. Clarified/updated the dialog nav/certcheck sections of KNOWN_ISSUES, brought the missing 0.27.0 and 0.33.1 branch changes from their ChangeLogs into NEWS, added a block in README describing all the plain text documents, added a note about making corrections to THANKS, a couple of TODO items, etc. * Note also that symlinks are now made from README-repos and README-renames to READMEs in the corresponding /etc/sbopkg/*.d directories. NOTE that renames files must now end in .renames so, if you have custom files in renames.d, you'll need to rename them. * The 'Choose a repository' dialog widget is now titled 'Repository Selection' and the widget text was revised. Also, the menu itself used to say 'BRANCH (REPO) DESCRIPTION' and now says 'REPO (BRANCH) DESCRIPTION'. The relevant item in the Utilities menu that shows which repo/branch you're on and takes you to the Repository Selection widget was similarly re-ordered. * When a repository directory does not exist, sbopkg now displays, e.g. REPO_{ROOT,NAME,BRANCH} -> /var/lib/sbopkg/,SBo/,13.1 or, in the case of git repos which don't currently have BRANCH directories, it just shows REPO_{ROOT,NAME}. It used to display REPO_ROOT -----------> /var/lib/sbopkg/ While the new line may be odd looking, it should be clear enough that it means REPO_ROOT is /var/lib/sbopkg/, REPO_NAME is SBo/ and REPO_BRANCH is 13.1 and that these are path components and that the path is missing. Before, it would say /var/lib/sbopkg/ didn't exist if, e.g., 13.1 was missing even when /var/lib/sbopkg/ did exist. BUGFIXES * Fixed an issue where URL redirects and SSL certificate check failures could combine to cause a download failure. Thanks to vbatts for raising this issue. * Fixed a documentation bug where the ability to keep a ~/.sbopkg.conf file to override the system config file (since 0.25.0) wasn't documented anywhere other than this file. It's now in both manuals. Thanks to Bill Kirkpatrick for raising this issue. * Fixed an issue where 'Invert all' in file removal dialogs didn't 'invert' but turned everything on or off, regardless of selection state. If it was really intended to be 'Select/Deselect all', then changing the button to "Invert Sel" and making it do that was a feature/modification instead of a bugfix. ;) * Fixed an issue were the user could switch repos, receive a directory creation prompt, abort it, and the active repo would be switched anyway, despite the directory not being created. Now, the original repo is restored as the active one. * Fixed a bug in a previous bugfix that would still let sbopkg download source files whose DOWNLOAD value ended in '/download' even when the source files were cached. * Fixed a depth-restriction bug triggered when an app directory's subdirectory has the same name as another app directory, causing sbopkg to match things or try to use things like openvswitch/xen/foo when xen/foo is intended. Thanks to David Somero for reporting this. From cnguyenminhtan at free.fr Thu Apr 28 21:11:44 2011 From: cnguyenminhtan at free.fr (cnguyenminhtan at free.fr) Date: Thu, 28 Apr 2011 23:11:44 +0200 (CEST) Subject: [sbopkg-users] How to make packages with one's own tag recognized by sbopkg In-Reply-To: <1022031059.1448481304024920818.JavaMail.root@zimbra10-e2.priv.proxad.net> Message-ID: <58074378.1449141304025104622.JavaMail.root@zimbra10-e2.priv.proxad.net> Hello, I've created packages using sbopkg and used a TAG option to change the "_SBo" tag because I wanted to share those packages on my site. This change of tag was needed in order to comply with guidelines regarding distribution of packages based on SlackBuilds.org scripts (refer to SBo FAQ #21). I've found out that those packages with renamed tags are not recognized as installed by sbopkg. I can understand such a situation but I'm curious to know if there exists (or is being planned) an option to enable custom tags to be recognized by sbopkg. I'm a bit light as a developer so I can not suggest a design/patch to implement such a feature. Thank you in advance for any clarification. Regards, Christophe From slakmagik at gmail.com Fri Apr 29 19:23:31 2011 From: slakmagik at gmail.com (slakmagik) Date: Fri, 29 Apr 2011 15:23:31 -0400 Subject: [sbopkg-users] How to make packages with one's own tag recognized by sbopkg In-Reply-To: <58074378.1449141304025104622.JavaMail.root@zimbra10-e2.priv.proxad.net> References: <1022031059.1448481304024920818.JavaMail.root@zimbra10-e2.priv.proxad.net> <58074378.1449141304025104622.JavaMail.root@zimbra10-e2.priv.proxad.net> Message-ID: <20110429192331.GA5197@devbox> On 2011-04-28 (Thu) 23:11:44 [+0200], cnguyenminhtan at free.fr wrote: > Hello, > > I've created packages using sbopkg and used a TAG option to change the > "_SBo" tag because I wanted to share those packages on my site. This > change of tag was needed in order to comply with guidelines regarding > distribution of packages based on SlackBuilds.org scripts (refer to > SBo FAQ #21). > > I've found out that those packages with renamed tags are not > recognized as installed by sbopkg. I can understand such a situation > but I'm curious to know if there exists (or is being planned) an > option to enable custom tags to be recognized by sbopkg. > > I'm a bit light as a developer so I can not suggest a design/patch to > implement such a feature. > > Thank you in advance for any clarification. > The best thing to do would be to create an additional repo file for your repository (see README-repos) or just replace 'SBo' with your tag in the local.repo file. You could even just run TAG=your_tag sbopkg if it would work well enough for you. If none of those work for you, let me know. BTW, could you please subscribe to the list? I have to individually approve people when they send mail as non-subscribers.