Sbopkg...
 

Hi Forum

Does the sbopkg tool keeps track of packages that I have installed w/ src2pkg...? installpkg'added packages...?

If not, which tool performs this... ? One may forget something is already instaled... and install another version over it...

BRGDS

Alex

there's no such tool: you have to look in /var/log/packages
everything you install from package is logged there.
if you copy something manually around or if you do the "./configure; make; make install" thing these won't be logged.

Sbopkg is a fantastic tool for installing and updating packages from SlackBuilds.org.

This will generate a file "addedpkgs.txt" listing all none standard Slackware packages (ones you've added):
This will show a list on screen :
Run them as root. Be careful when running the second one - be sure to hit cancel.

As far as I'm aware sbopkg looks for "_SBo" as a "repository tag" in package names of packages in /var/log/packages. In effect this will miss your own installed packages if they don't have this tag.

I use my own tag with sbopkg, so I build packages tagged "ponce" and sbopkg recognize that tag for upgrades,lists,etc.
I have added the line
in /etc/sbopkg/sbopkg.conf and edited /usr/sbin/sbopkg substituting this line (978 in the latest version)
with
no way to set it in conf because it's unset in sbopkg script before being set to that value.

You can always just run pkgtool and choose to view the files in a package which will show you a list of all packages installed. I use a ROX AppDir which I came up with which offers a few functions like a quick listing of the packages(ls -1 /var/log/packages), a dialog for searching for which package installs a ceratin file, or a function which searches for a file in the MANIFEST listing of all the available packages (since I only install about 25% or less of the available ones). Just dropping a package on the AppDir installs it, or just clicking the icon runs the normal pktool.

@poncez: Thanks for that idea - it's quite a good one. I briefly looked through the sbopkg script to see that REPO_TAG information but didn't think of customizing that code to suit :doh: - good thinking.

glad you liked it, remember only to reedit when you upgrade sbopkg ;)

Or better yet, file this as a feature request. :-)

Hi, Chess, and thanks for replying. I have been having a look at the Google Code project for Sbopkg and the Sbopkg home page but can't find a place to submit such a request. Apologies if I'm being dumb and missing something obvious! What's the preferred way of doing this ?

Allrighty ppl,

So I have installed sbopkg, it is now syncing after having created all those dirs,..

Since I have a Slackware64 13, I have to change the arch in all the slackbuilds I have used... so... If I use sbopkg to Install/update anything, will it handle this arch thing automatically for me, or will I still have to nano...*.SlackBuild to change ARCH to x86_64...?

BRGDS

Alex

nope. edit yourself.

no no no...am sorry...thats not my answer, i was having internet connection problems and could not edit properly. here is the full post: am terribly sorry :(

sbopkg is a great tool imho.

Alexvader

ARCH is set automatically according to your architecture afaik.

'upgradepkg --install-new PACKAGENAME' command makes sure that package gets upgraded when there's another version of it already installed. When there's no other version of the software installed it installs new package.

For keeping an eye on /var/log/packages i use 'qtgsmanager' which is third party unsupported gui frontend for pkgtools, but has nice featureset and does not have to be run as root for basic operations.

Hi ppl

Thks for yr replies,

@Slackd,@Shylock : Ok, I have already used sbopkg, but hand edited the SlackBuild in the interactive window to change ARCH, glad to hear it is automatic... :-)

@veeall : I will try this one... :-)

BRGDS

Alex

Sorry for the delay in responding ... you can file it in the "Issue Tracker" at the sbopkg Google Code page you linked to. The Issue Tracker is used for bug reports, feature requests etc.

tnx chess, just filed the feature request :)

Poncez, great thanks. That helps us keep track of things.

One thing I mentioned there that I will mention here in case someone else finds this thread is that sbopkg might already be able to do what you want. Look into creating a 'local' repo (i.e. a custom repo) where you can have your own packages. See the README-repos.d documentation file for more information.

I agree with this sentiment and am surprised that sbopkg is not prominently mentioned on the Slackbuilds website as a tool that can really enhance the usefulness of the site and its builds. As far as I could tell there was not even an sbopkg Slackbuild to be had from the site. How come ?

Bogus

I didn't want to create new thread for this question about ncurses/sbopkg: Is it possible to select a text displayed in ncurses dialog boxes - for example in README files displayed by sbopkg? Then it would be possible to create a queue file just by middleclick-pasteing dependencies from displayed README-s to a 'nano' editor on another konsole window.

If you're in X or have gpm running on a vt, you can hold shift while selecting and click to paste.

Thank you a lot for this tip! I didn't know that one.

There are several reasons:

1. I already provide a package on the sbopkg website (which includes the SlackBuild I use to create the package) so for me to create and maintain a SlackBuild script for sbopkg at SlackBuilds.org seems like a duplication of effort, IMHO (but, see #3).

2. I think it is important to keep a separation between SlackBuilds.org and sbopkg itself since SlackBuilds.org does not officially support or endorse sbopkg. Mentioning it in the FAQ might make some folks think the SlackBuilds.org admins provide support for sbopkg itself, and questions/bug reports to them would waste their time and not get to the right place (viz, the sbopkg team).

3. Notwithstanding #1, if someone thought it would be beneficial to have a sbopkg SlackBuild script at SlackBuilds.org, they are free to give it a go. However, nobody has created the script (or taken the one I provide) and submitted it to SlackBuilds.org. It might be the case that if someone else wanted to create and maintain a SlackBuild script for sbopkg in the SlackBuilds.org repo, it would be accepted.

ARCH is only set automatically if sbopkg finds that you are running x86_64. If you aren't then you can set it on the command line:

ARCH=i686 sbopkg

You could set it as an environmental variable, but that tends to give problems when compiling kernel modules.