As ponce said, testing/ is not a different "native Slackware". There is no slackware-testing/ version on your favorite mirror like there is for the stable releases and -current. It is just a place for Pat to put things that are for testing. testing/ directories exist for every version of Slackware, both stable releases and -current, and packages may go in and out of there without warning. It also typically contains configs for newer kernels versions than the release contained.

You don't, I know. Running slackpkg+ will not let you know that the packages are from testing. They will appear as upgrades along with anything not in testing.

But it also is a strange feature to have this below

set in slackpkg.conf.

But slackpkg never uses that testing. So why is it there? Was it added so slackpkg+ can use it?

The testing subdirectory is simply an optional gift from Patrick. Why do you want to analyse it to death?

You need to understand:

* -current is for people who understand the whole distro, it's not for people who only know how to use slackpkg
* slackpkg is a convenience, it's not intended as a complete management tool
* slackpkgplus is separate to slackpkg, it's unofficial and still evolving

PRIORITY= is nothing to do with slackpkg, if you have complaints about PRIORITY= you should either (1) edit your config, or (2) talk to the slackpkgplus developers, they are really helpful.

1 members found this post helpful.

Haha, it's provided by slackpkg.

Did you read the comments in the line right above PRIORITY= ...? Testing being last in the PRIORITY list means that it will search there last for packages. So let's say you type slackpkg install somepackage. It will look in all those other repositories first before searching testing. So the only time slackpkg will install something from testing is if it is a new package that does not exist anywhere else in Slackware yet. Of course, you could move testing higher up the list if you want to risk great destruction to your system.

No, but by slackpkgplus that is not shipped in Slackware.

1 members found this post helpful.

The line he's talking about is in slackpkg.conf, which is shipped with Slackware.

1 members found this post helpful.

- I don't have slackpkg+ installed here, just slackpkg;
- I've set testing with an higher priority in /etc/slackpkg/slackpkg.conf (read: it comes first in the list, not last);
- if I do a "slackpkg upgrade-all" it proposes me to install the efibootmgr and gcc packages from /testing.
I have no idea why it behaves differently for you.

That's right, I stand corrected.

My (very bad, I admit, but please no flamewar for that) excuse is: as I favor slapt-get over slackpkg and slackpkgplus I didn't remember at first. I should have checked before writing, though, sorry.

You're right; apologies about that.

Then that should only get installed via install-new not upgrade-all. If that's the current behavior then that's a very unexpected feature or a bug.

I'd consider that as a default behavior to be a Very Bad Idea (tm).

5 members found this post helpful.

I don't understand what you are saying. Do you mean that you ran slackpkg upgrade-all and it upgraded your regular packages with versions from testing? If so, you're right that that shouldn't be happening, unless you changed the order of testing in the PRIORITY variable.

That is not the default behaviour. With an unchanged /etc/slackpkg.conf and after installing the slackpkg+ package from http://slakfinder.org/slackpkg+/ and not changing /etc/slackpkgplus.conf , the resulting behaviour of slackpkg is unaltered from when slackpkg+ was not installed. The /testing directory does not have preference over anything, and the packages in there (gcc and efibootmgr) are never shown during a "slackpkg upgrade-all" or "slackpkg install-new" as a candidate for upgrading or installing.

It is only when you move the word "testing" on the PRIORITY definition in /etc/slackpkg.conf all the way to the front, so that the 'testing' packages have priority over anything else in the Slackware repository (a bad thing to do unless you want to be bitten sometime), that a "slackpkg upgrade-all" command will show you a package found in testing (gcc and efibootmgr) as candidates for upgrading the regular versions of those packages. And with slackpkg+ installed (unaltered configuration file) you will notice that slackpkg will even show you in its package list that this package was found in testing instead of in the slackware64 repository. See screenshot.

I think it is time you accompany your statements on LQ with actual evidence. Please show us here what commands you use, what results you get, and what you changed in /etc/slackpkg.conf , /etc/slackpkg/mirrors and /etc/slackpkgplus.conf (if you do not remember what you changed, just post the full files). Lots of people are wasting their precious time in trying to argument something they know is right and you are countering it just with words and accusations, not facts and proof. Please do better than that.

Attached Thumbnails

 

7 members found this post helpful.

Based on recent threads I am pretty sure OP is just trolling. Time to add to the ignore list.