[SOLVED] installing package final step on slackbuilds doesnt work
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.
Well I have Slack 14 installed and in the /etc/slackpkg/mirrors file Slack 14 & current are there 13.37 isn't an option so thats not the issue i'm facing.
It seems to be any package. I tried several all from different catagories. These are my steps:
1. download source and slackbuild into build dir
2. untar slackbuild tarball & mv source tarball into slackbuild untared folder
3. cd to slackbuild folder and change version if applicable
4. chmod +x slackbuild then execute with ./ *as root
5. cd /tmp & slackpkg install whichever *as root
outputs
Code:
slackware No packages match the pattern for install Try:
/usr/sbin/slackpkg install|reinstall
@Dman58: FWIW slackpkg is actually just a nice extra, not the main Slackware package manager or to put it another way it is not an essential component of pkgtools like installpkg, upgradepkg, removepkg and makepkg are (IMHO).
In fact, if you have a full install and run stable you could easily do without slackpkg (if you so desired) since its primary use in such a scenario is simply fetching updates (patches). I rarely use it and instead use my own script that simply fetches patches for those programs I have installed. When I upgrade Slackware, I use an official DVD (since I have a subscription) with upgradepkg and removepkg.
Slackpkg is most useful when you track -current and/or if you have a minimal install and occasionally want to add apps over the network, without maintaining a local mirror.
FWIW slackpkg is actually just a nice extra, not the main Slackware package manager or to put it another way it is not an essential component of pkgtools like installpkg, upgradepkg, removepkg and makepkg are (IMHO).
In fact, if you have a full install and run stable you could easily do without slackpkg (if you so desired) since its primary use in such a scenario is simply fetching updates (patches). I rarely use it and instead use my own script that simply fetches patches for those programs I have installed. When I upgrade Slackware, I use an official DVD (since I have a subscription) with upgradepkg and removepkg.
Slackpkg is most useful when you track -current and/or if you have a minimal install and occasionally want to add apps over the network, without maintaining a local mirror.
Thanks, I'll try to keep that in mind. I'm sure I read that somewhere before but after reading sooo many different guides, tutorials, howtos, etc. I guess certain things just slip away in the distance until they are directly needed again.
I appreciate all the feedback here at LQ and I'm humble on my Linux journey!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.