SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
It allow to add directory without metadata in config file
all packages must be in a single directory; no subdirectory supported.
For these repositories, slackpkg update is not needed.
When you add a package in directory it will automatically recognized.
It's most useful for who install a personal package and don't want to insert it in blacklist.
PKGS_PRIORITY=( mypackages:.* )
to override slackware packages and to be sure that slackpkg upgrade-all no more will ask you to reinstall original package.
When you upgrade a package, copy it in directory and run slackpkg upgrade-all (or slackpkg upgrade mypackages)
This version also supports a new enviroment variable: 'USEBL' (alias USE BLACKLIST). You can put it in slackpkgplus.conf but isn't useful. That variable is to use to temporary skip blacklist file.
I recompile gcc myself, so I put it in blacklist. Now to known if Patrik release a new version (so I must to recompile) I've to monitor the Changelog, but I can also run
search and file-search are buggy. I sent a patch to fix it at slackpkg's website.
Patched core-functions.sh to fix searching for qt, phonon, and other
packages in cases where package names overlap.
Thanks to Sébastien Ballet.
The README on slackware/source/ap/slackpkg tell: "slackpkg" is a shell script, so there is no source package.
But where is the slackbuild, the original script, and the included patch? The official download page contains slackpkg-2.82.0-noarch-2.tgz
However we must to test if that slackpkg version impact slackpkg+
Slackware 14.1 is sufficently stable to call it 'rc1'.
Also I think that slackpkg+ is sufficently mature, so I finally call it 1.0rc1
Latest slackpkg 2.82.0-11 include the (not currently existing) 14.1 official repository becouse when stable release will be released that repositories will be immediatly created.
Unfortunatly I can't add 14.1 third-party repository in slackpkg+ unless I don't know which repositories will be quickly created.
If you know that your repository will be alive in a short after slackware release, you can tell me here and I will add it.