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.
Not that it's an issue, but when using 'slackpkg download' it's a count, not a percentage. I personally am okay with this. I normally only use "download" with kernel packages. Just thought I'd mention it.
Not that it's an issue, but when using 'slackpkg download' it's a count, not a percentage. I personally am okay with this. I normally only use "download" with kernel packages. Just thought I'd mention it.
Unfortunately the 'download' command is not 100% slackpkg+ compliant so it is not fully supported.
Use DOWNLOADONLY switch instead.
set it in slackpkgplus.conf or use
DOWNLOADONLY=on slackpkg install ...
Sun Mar 8 13:58:45 CET 2020
pkg/slackpkg+-1.7.0d1-noarch-8mt.txz
- Extends percentage where possible.
- Align check-updates messages with slackpkg 2.84
- Catch errors and return exit status: 1 for warning, 2 for fatal
it adds the httpdir:// httpsdir:// ftpdir:// repositories type.
Similar to dir:/ it allow to add in configuration repositories that have no metadata (single packages into a single directory)
for example:
Unfortunately the 'download' command is not 100% slackpkg+ compliant so it is not fully supported.
Use DOWNLOADONLY switch instead.
set it in slackpkgplus.conf or use
DOWNLOADONLY=on slackpkg install ...
I only use 'slackpkg download kernel' and it works. Put the downloads in "/var/cache/packages/slackware64/*/*" This form also works 'slackpkg download kernel-generic kernel-headers kernel-modules kernel-source'
After I an done installing the packages I 'rm' them from "/var/cache/packages/slackware64/*/*"
I will try the DOWNLOADONLY switch next kernel update.
slackpkg download is not fully supported by slackpkg+ but it should work in many cases.
Thanks, just wanted to let you know it does work (in at least my use case).
Quote:
Originally Posted by zerouno
I'm testing a new feature...
it adds the httpdir:// httpsdir:// ftpdir:// repositories type.
Similar to dir:/ it allow to add in configuration repositories that have no metadata (single packages into a single directory)
Wow, that's a cool feature.
Working here. Tested "httpsdir://" with "slackpkg.org/beta".
I have discovered, that in my "PKGS_PRIORITY" above, if I place "slackpkgbeta" anywhere in the array before the "slacware64:..." entries it works as expected. Placing "slackpkgbeta" at the end or before "alienbob" produces:
I can see the "slackware64:... alienbob" items being together since I am specifically overriding those packages in "alienbob". I would think that placing "slackpkgbeta" at the end though should show the correct list. Now that's not normally were I would put "slackpkgbeta" anyway but on my first run with the new feature, that is were I placed it.
BTW, I think slackpkg+ is the greatest thing since sliced bread. I've been using it for sometime now. Love it.
Last edited by chrisretusn; 03-09-2020 at 11:57 AM.
I have discovered, that in my "PKGS_PRIORITY" above, if I place "slackpkgbeta" anywhere in the array before the "slacware64:..." entries it works as expected. Placing "slackpkgbeta" at the end or before "alienbob" produces:
I can see the "slackware64:... alienbob" items being together since I am specifically overriding those packages in "alienbob". I would think that placing "slackpkgbeta" at the end though should show the correct list. Now that's not normally were I would put "slackpkgbeta" anyway but on my first run with the new feature, that is were I placed it.
BTW, I think slackpkg+ is the greatest thing since sliced bread. I've been using it for sometime now. Love it.
my bad. there's a (stupid) bug in searchPackages(). The patch below (also in attachment) solves this. However, it would be better to make further tests before applying it to slackpkg+ stable.
Code:
--- slackpkgplus.sh.orig 2020-03-09 21:06:56.680005136 +0100
+++ slackpkgplus.sh 2020-03-09 21:06:56.680005136 +0100
@@ -1155,7 +1155,7 @@
# extract the pattern from $i, if and only if "$i" is to the syntax <repo>:<pattern>. Without
# this, PAT would be set to $DIR when $i is to the syntax <repo>.
#
- [[ "$DIR" =~ [:][:alnum:]+ ]] && PAT=${i/*:/}
+ [[ "$i" =~ [:][[:alnum:]]+ ]] && PAT=${i/*:/}
# when the current priority is of kind <REPO>:<PATTERN>, the loop must be short-circuited
# when SEARCHSTR does not match PATTERN, otherwise, some packages could be mistakenly
The list below shows the packages that contains "slackpkg" file.
[ Status ] [ Repository ] [ Package ]
installed extra bash-completion-2.10-noarch-1
installed slackpkgplus slackpkg+-1.7.0d1-noarch-9mt
upgrade slackware64 slackpkgbeta:slackpkg-2.84.0_beta8-noarch-1_rlw --> slackpkg-2.83.0-noarch-4
You can search specific packages using "slackpkg search package".
This patch also appears to have solved another issue I was seeing. The placement of "repository:package". If you note in the above codebox, I have the "slackware64:package" entries before the "alienbob" repository entry. If I am reading the slackpkg+ docs correctly the "slackware64:package" priority must be before "alienbob" because I am telling slackpkg+ to give priority to "slackware64" over "alienbob". This placement also makes sense to me as only "alienbob" is being overridden.
The issue I WAS seeing is, if I placed the "slackware64:package entries anywhere else I would get "upgrade" in the list for alienbob instead of "installed".
Code:
Example
[ Status ] [ Repository ] [ Package ]
upgrade alienbob slackware64:id3lib-3.8.3-x86_64-2 --> id3lib-3.8.3-x86_64-1alien
Now, no matter where I place those "slackware64:package" entries, except of course after "alienbob" it works as I think it should. An extreme example follows:
At first, even with the patch installed, I was seeing the issue I just described; however, now I cannot reproduce it. Just to be sure I cleared the cache and also data directories (probably overkill but doesn't hurt). Seems to be working correctly.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.