SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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.
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
Code:
export TAG=ponce
in /etc/sbopkg/sbopkg.conf and edited /usr/sbin/sbopkg substituting this line (978 in the latest version)
Code:
REPO_TAG=${REPOSITORIES[$((i + 3))]}
with
Code:
REPO_TAG=ponce
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.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
Quote:
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
@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 - good thinking.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
Quote:
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 ?
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...?
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...?
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
Quote:
ABOUT $ARCH
You may be wondering why $ARCH is not a configuration setting in the
sbopkg.conf file. The reason is that it does not have to be. First,
sbopkg does some checking (using 'uname -m') to determine what the sys-
tem's architecture is. If the architecture is x86_64, then sbopkg
automatically sets ARCH=x86_64. If the architecture is not x86_64,
then sbopkg will inherit any $ARCH settings in the environment. This
means, the user can add, for example, 'export ARCH=i686' in their
.bashrc or similar file, or the user can also execute something in the
root terminal like 'export ARCH=i686 && sbopkg'. The user can also
manually add it to their sbopkg.conf file if they wish. Finally, if
$ARCH is not set by the user and sbopkg does not detect an x86_64 sys-
tem, then $ARCH will default to whatever $ARCH is set to in the Slack-
Build scripts.
'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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.