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.
See README for details (and, if you want, send me a patch to correct the english grammatical errors )
I think that this release maybe an rc to 1.0 (but I've idea for some other feature before release), but I want to wait your feedback and bug report on these features.
See README for details (and, if you want, send me a patch to correct the english grammatical errors )
I think that this release maybe an rc to 1.0 (but I've idea for some other feature before release), but I want to wait your feedback and bug report on these features.
Maybe export existing packages on the sistem list to a file and imoport of that file to install packages that are not in the another or new system would be an good idea?
Maybe export existing packages on the sistem list to a file and imoport of that file to install packages that are not in the another or new system would be an good idea?
It allow to add directory without metadata in config file
MIRRORPLUS['mypackages']=dir://path/to/packages/
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.
set
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.
today included!
from changelog:
Quote:
ap/slackpkg-2.82.0-noarch-10.tgz: Rebuilt.
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+
ap/slackpkg-2.82.0-noarch-10.tgz: Rebuilt.
Patched core-functions.sh to fix searching for qt, phonon, and other
packages in cases where package names overlap.
Thanks to Sébastien Ballet.
However we must to test if that slackpkg version impact slackpkg+
The inclusion of this patch has no consequence over slackpkg+. It only affects the function makelist() which is not used by the slackpkg+ search, which relies on :
the function searchPackages(), starting at line #271
the function searchListEX(), starting at line #348
the if block starting at line #680, which ends with a call to cleanup() to short-circuit the execution of original slackpkg search.
yes but in the world at least one people will type 'makepkg slackpkg-2.82.0-noarch-10.tgz' to create that package!
You can, no problem.
Code:
# mkdir -p /tmp/bogus
# cd /tmp/bogus
# explodepkg /path/to/slackpkg-2.82.0-noarch-10.tgz
# ... edit here and there...
# makepkg -l n -c n /path/to/slackpkg-2.82.0-noarch-11.tgz
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.
Well here is some of the stuff for Slackware 14.1 that could go into slackpkgplus.conf - note that you can change "14.1" for "14.0" or "13.37" if that is the version of Slackware you are running:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.