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.
root@localhost:/tmp# which slackpkg
/usr/sbin/slackpkg
root@localhost:/tmp# slackpkg install slackware
Looking for slackware in package list. Please wait... DONE
No packages match the pattern for install. Try:
/usr/sbin/slackpkg reinstall|upgrade
root@localhost:/tmp# /usr/sbin/slackpkg reinstall|upgrade
bash: upgrade: command not found
root@localhost:/tmp#
Apparently, I don't know how to use it fully either. I thought that install-new would install any missing packages. But you should be able to run (I think -- I don't use slackpkg much)
Code:
slackpkg install d
slackpkg install l
This corresponds with the categories I mentioned earlier. I tried looking for a page that covers the various categories as I'm sure I've seen it in the past, but my google-fu skills are weak today.
bassmadrigal,
"slackpkg install-new" installs only "new" packages, i.e. marked with "Added" in ChangeLog.txt as we can see in "man slakpkg" and slackpkg bash script itself.
@bormant, thanks! That makes sense. I didn't have easy access to my computer (would've had to ssh in through my phone) and just glanced at some stuff online for it (and slackpkg's main site is blocked at my work).
Apparently, I don't know how to use it fully either. I thought that install-new would install any missing packages. But you should be able to run (I think -- I don't use slackpkg much)
Code:
slackpkg install d
slackpkg install l
This corresponds with the categories I mentioned earlier. I tried looking for a page that covers the various categories as I'm sure I've seen it in the past, but my google-fu skills are weak today.
Where is there documentation on the "PATTERN" use of slackpkg in terms of identifying what "d" or "l" stand for. The man page for slackpkg show the format, but I am unable to find anything on the web, much less Slackware's site, the shows what the choices are or the meaning of "d" and "l". I'm guessing there is some directory somewhere for packages and these patterns select certain directories. I want to upgrade a sparse image file to a full system; however, I'd like to avoid the kde* stuff, if possible.
== Edit ==
And I really would like to avoid the multi-language stuff -- I do not need Calligra installed for multiple languages. Is there a setting that specifies only a particular language, e.g. "en"?
It's perhaps worth pointing out that if you'd installed the way God intended (via the installer) you'd already have been introduced to these categories
It's perhaps worth pointing out that if you'd installed the way God intended (via the installer) you'd already have been introduced to these categories
I used stacklet's image for a XEN server. One of the benefits of a Virtual Machine server such as XEN is that it's suppose to be convenient to deploy a build of Linux. What I have learned from this experience, and from the quoted statement above, is that stacklet's image of Slackware is not a viable system for building with MinGW unless you completely rebuild it with all the bells and whistles.
TIP: for those who might be trying to use an image on a XEN server to create an instance of Slackware, know that you will need to increase the size of the sparse file image in order to accommodate a full load of what "God intended" as referenced above.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.