Main menu:

Sponsoring

Please consider a small donation:

 

Also appreciated: support me by clicking the ads (costs nothing) :-)

 

Or you can donate bitcoin:

 

Thanks to TekLinks in Birmingham, AL, for providing colocation and bandwidth.

Page Rank

Fame

FOSS Force Best Blog--2013 Award

Recent posts

Recent comments

About this blog

I am Eric Hameleers, and this is where I think out loud.
More about me.

Search

My Favourites

Slackware

Calendar

April 2014
M T W T F S S
« Mar    
 123456
78910111213
14151617181920
21222324252627
282930  

RSS Alien's Slackware packages

RSS Alien's unofficial KDE Slackware packages

RSS Alien's multilib packages

Tag cloud

Meta

Introducing slackpkg+, an extension to slackpkg for 3rd party repositories

I want to introduce you to a tool written by Matteo Rossini (nicknamed zerouno of the Italian slacky.it community and contributor of several SlackBuild scripts at SlackBuilds.org as well as creator of the Slackware package search site slakfinder.org) with some serious contributions from phenixia2003, author of compat32pkg.

The tool is “slackpkg+“. It is not a stand-alone piece of software. In fact, it is an extension to Slackware’s package manager “slackpkg“. I will first describe the strengths of “slackpkg” and then come to the reasons why “slackpkg+” was written.

Slackpkg itself is a wrapper around the Slackware pkgtools (installpkg, upgradepkg, removepkg) with built-in package search capabilities and very useful when you want to keep your Slackware installation up to date. It was written with a modular design in mind: it can be extended with new functionality by adding new or extending existing functions in the “/usr/libexec/slackpkg/functions.d/” directory.

Slackpkg is my preferred tool for system upgrades (i.e. upgrading from one Slackware release to the next). People who do not use slackpkg usually have to do much more handywork like reading ChangeLog.txt entries for package additions, updates and removals, and/or follow the official Slackware guideline as found in “UPGRADE.TXT“. One disadvantage of the instructions found in UPGRADE.TXT is that the suggested “upgradepkg –install-new *.t?z” command will install every package you did not yet have installed – not just the packages that were introduced in the latest Slackware release but also the packages which you did not want to install anyway in the past.

Slackpkg allows you to keep full control over the packages that get installed, by showing you lists of candidate packages for every action you want to perform. You can de-select any package you do not want to be acted upon.

So far its strengths. The most heard “complaint” about slackpkg is that it will install and upgrade packages only from official Slackware repositories – it does not support 3rd party package repositories. This is why some users switch to other (unofficial) package managers like slapt-get, which do support 3rd party repositories. Slackware spin-offs like Salix and Vector use slapt-get. Slackpkg also does not allow you to keep a Slackware multilib installation correctly updated. The community tool compat32pkg was written for that purpose.

Both these issues (3rd party repository support and multilib support) are addressed in the slackpkg+ extension to slackpkg.

Slackpkg+ is NOT a new tool with new commands. Because it extends slackpkg, you can continue to use the well-known slackpkg commands after adding your 3rd party repository configuration:

# slackpkg update gpg
# slackpkg update
# slackpkg install openjdk
# slackpkg upgrade-all

etc..

The slackpkg+ extension also extends the search functionality in slackpkg:

# slackpkg search vlc    

DONE

The list below shows all packages with name matching "vlc".

[ Status           ] [ Repository               ] [ Package                                  ]
   installed           alienbob                     phonon-vlc-0.6.0-x86_64-1alien            
  upgrade              alienbob                     npapi-vlc-20130818-x86_64-1alien --> npapi-vlc-20130408-x86_64-1alien  
  upgrade              alienbob                     vlc-20130819-x86_64-1alien --> vlc-2.0.8-x86_64-1alien  
   installed           alienbob_current             npapi-vlc-20130818-x86_64-1alien          
   installed           alienbob_current             vlc-20130819-x86_64-1alien                
  upgrade              restricted                   npapi-vlc-20130818-x86_64-1alien --> npapi-vlc-20130408-x86_64-1alien  
  upgrade              restricted                   vlc-20130819-x86_64-1alien --> vlc-2.0.8-x86_64-1alien  
   installed           restricted_current           npapi-vlc-20130818-x86_64-1alien          
   installed           restricted_current           vlc-20130819-x86_64-1alien                

You can search specific files using "slackpkg file-search file".

You probably noticed that the package “vlc” is listed several times in this search exxample. That happens because I have this package in several repositories. You can (as shown further down) configure slackpkg+ with the correct priority in which these repositories are consulted when installing/upgrading software, so that the correct package will always be used.

Let me show you how I use slackpkg+ to maintain my computers.

I run Slackware-current 64-bit, with multilib added. I install my packages from multilib-current as well as my Slackware 14.0 package repository. Sometimes, I create a package specifically for Slackware-current (such as calibre, vlc, …) because the Slackware 14.0 version of that package will not work on Slackware-current. In such a case I want slackpkg to install the -current package and not the 14.0 package.

This is my configuration file “/etc/slackpkg/slackpkgplus.conf”:

SLACKPKGPLUS=on
PKGS_PRIORITY=( multilib:.* restricted_current:.* restricted:.* alienbob_current:.* alienbob:.* ktown:.* )
REPOPLUS=( slackpkgplus multilib ktown alienbob alienbob_current restricted )
MIRRORPLUS['alienbob']=http://192.168.0.1/slackware/sbrepos/14.0/x86_64/
MIRRORPLUS['restricted']=http://192.168.0.1/slackware/restricted_sbrepos/14.0/x86_64/
MIRRORPLUS['slackpkgplus']=http://slakfinder.org/slackpkg+/
MIRRORPLUS['multilib']=http://192.168.0.1/slackware/multilib/current/
MIRRORPLUS['alienbob_current']=http://192.168.0.1/slackware/sbrepos/current/x86_64/
MIRRORPLUS['restricted_current']=http://192.168.0.1/slackware/restricted_sbrepos/current/x86_64/
MIRRORPLUS['ktown']=http://192.168.0.1/ktown/current/latest/x86_64/

A breakdown of these lines:

  • You will notice that I have a local webserver running in my LAN (IP address 192.168.0.1) but you can use any public webserver which hosts these repositories. Having the repositories mirrored locally in the LAN has benefits for download speeds of course.
  • The variable “SLACKPKGPLUS” determines whether the functionality of slackpkg+ will be enabled at all. If you set it to”off” then slackpkg will not use any of the new code. The default is “on”
  • The “MIRRORPLUS” variables define an array of 3rd party repositories which you want slackpkg to know about.The array indices of the MIRRORPLUS array (like ‘alienbob’, ‘restricted’, ‘ktown’, etc…) are used in other variables, as will be explained next:
  • The “REPOPLUS” variable defines which of the 3rd party repositories you have defined in MIRRORPLUS are actually actively used. The order in which the repositories are mentioned is not important.
  • That repository order is important in the “PKGS_PRIORITY” variable. With this variable, you can force priority for certain repositories, or even for individual packages in these repositories. For instance, having “multilib:.*” listed first, means that my multilib package always have priority over the Slackware versions of these packages (gcc and glibc to be specific). Also, by defining the order “alienbob_current:.* alienbob:.*” I will ensure that when a package (such as calibre) is found in both repositories, slackpkg will install the one from the “-current” repository. The “.*” behind the repository’s name is a wildcard meaning “any package“. If you want you can make that more specific, like “restricted:vlc” which means “the vlc package in the ‘restricted’ repository“.

NOTE:

You will probably have added 3rd party packages to your slackpkg blacklist. When you install slackpkg+ you should of course remove those blacklist lines! If you don’t, then slackpkg will never show those blacklisted packages…

For instance, the lines you need to remove from “/etc/slackpkg/blacklist” in order to let slackpkg/slackpkg+ manage my packages, are:
[0-9]+alien
[0-9]+compat32

NOTE:

Similar to enabling a Slackware repository for your specific Slackware version and architecture in /etc/slackpkg/mirrors , you will add additional 3rd party repositories in /etc/slackpkg/slackpkgplus.conf . Take good care that you only add repositories which contain packages compatible with your particular version and architecture of Slackware ! The example repositories which I showed you above are suited for my Slackware64-current-with-multilib installation. If you are running Slackware 14.1 you should add repositories that offer packages for Slackware 14.1.

As a rule of thumb, do not mix packages for different versions of Slackware. Specifically, do not attempt to install packages for a more recent version of Slackware than you have installed on your computer. Most packages built for an older release of Slackware will still work on newer versions of Slackware (as an example, Slackware64-current contains several packages that have not changed since 13.0 and those still work).

CAVEAT:

The slackpkg tool parses the Slackware ChangeLog.txt to determine which packages are being added to Slackware. It looks for strings like “Added.” in the changelog when you run the command “slackpkg install-new”. This functionality does not work for 3rd party repositories. That means I can not simply run “slackpkg upgrade kde” to get my newest KDE “ktown” release installed – any package which is not present in Slackware itself, will not be installed with that command. On the other hand; keeping your “ktown” installed packages up to date afterwards, is easy with slackpkg+ because it will detect any upgrade to individual packages. .

The “slackpkg+” extension has its homepage on http://slakfinder.org/slackpkg+.html You can find more of slackpkg+ here:

If you have a set of packages that are not part of any repository yet, and you want to create your own slackpkg+-compatible repository for them, you should check out an older article on this blog: http://alien.slackbook.org/blog/local-slackware-mirror/ . In there you will find an explanation about how to use my “gen_repos_files.sh” script.

Have fun! Eric

Comments

Comment from Niki Kovacs
Posted: August 25, 2013 at 16:34

Thanks for that detailed article, Eric. This nifty tool has completely changed the way I maintain Slackware, and it’s made everything so much easier. Whether it’s a server, a desktop or a workstation, I can issue a simple “slackpkg search microlinux” and have a detailed overview of what extra packages are installed, which ones need upgrading and what’s missing. Love it, and couldn’t to without it anymore.

BTW, I *think* that Matteo Bernardini is ponce, not zerouno. Correct me if I’m wrong.

Comment from Marco Lavorini
Posted: August 25, 2013 at 18:02

@Niki Kovacks: You are right,
ponce is Matteo Bernardini and zerouno is Matteo Rossini

Comment from Bb
Posted: August 25, 2013 at 18:24

@alienbob Thanks for this post… I’ve been waiting for slackpkg+ to be considered stable to start making use of it, and it looks like that time has come! What’s the best work-around for the CAVEAT? Say I want to upgrade to the latest KDE in ktown and there are some new packages. Do I need to know which new packages need to be installed (by reading your release notes for example) and do the installation manually with “slackpkg install”? Thanks.

Comment from alienbob
Posted: August 25, 2013 at 18:44

Oops, I make that name switch constantly… fixed it in the article. Sorry ponce & zerouno!

Eric

Comment from Matteo Rossini
Posted: August 25, 2013 at 20:59

Yes, I’m Rossini, but the contributor of SBo is Bernardini (ponce).

The workaround for the CAVEAT is
slackpkg upgrade kde && slackpkg install kde
but to upgrade kde you must also remove slackware package “kdeadmin kdenetwork kdesdk kdetoys”, with removepkg or with slackpkg remove kdeadmin kdenetwork kdesdk kdetoys.
The “slackpkg clean-system” does not help here.

For REPOPLUS “The order in which the repositories are mentioned is not important.”, is not true.
The order is honoured by slackpkg+, so if you put into REPOPLUS ” alienbob restricted “, then slackpkg installs vlc from alienbob, but PKGS_PRIORITY has _most_ precedence.
The order is:
1) PKGS_PRIORITY’s packages as listed;
2) SLACKWARE packages
3) REPOPLUS’s as listed
If you put into PKGS_PRIORITY ” alienbob:.* ” and that repository contains slackware packages, they will be installed and slackware packages ignored;
if you put into REPOPLUS ” alienbob “, slackware packages have precedence.

Zerouno

Comment from Niki Kovacs
Posted: August 25, 2013 at 23:07

Thanks for the great work, Zerouno. And BTW, I noticed you added two of my repos to the configuration file. I’m honoured.

Comment from Bb
Posted: August 25, 2013 at 23:09

Thanks for the tips Matteo, that’s really great info.

I have another question. I am using the following in my slackpkgplus.conf:
REPOPLUS=( alienbob restricted slackpkgplus )
MIRRORPLUS['alienbob']=http://taper.alienbase.nl/mirrors/people/alien/sbrepos/current/x86_64/
MIRRORPLUS['restricted']=http://taper.alienbase.nl/mirrors/people/alien/restricted_sbrepos/current/x86_64/
MIRRORPLUS['slackpkgplus']=http://slakfinder.org/slackpkg+/

However, “slackpkg search vlc”, for example, returns nothing. In fact, nothing from alienbob or restricted works for “search” or “install”. I can search and for install slackpkg+ from the slackpkgplus repo. I can also use “slackpkg info” for any of the alienbob or restricted packages, and if I look in “/var/lib/slackpkg/” I can see all the packages from alienbob’s repos, such as:

SLACKPKGPLUS_alienbob vlc 20130819 x86_64 1alien vlc-20130819-x86_64-1alien ./SLACKPKGPLUS_alienbob/vlc txz

Can anyone tell me what I am doing incorrectly?

Comment from escaflown
Posted: August 25, 2013 at 23:54

I have the exact same settings as Bb and “slackpkg search vlc” doesn’t return any result. I can see the vlc in Eric’s repository though.

Comment from lms
Posted: August 26, 2013 at 12:57

I had the same problem, with “slackpkg search vlc” not giving any result… I found that I had to remove the alien packages from slackpkg blacklist file.

Comment from Bb
Posted: August 26, 2013 at 14:05

@lms of course! Works fine now… Thanks!

Comment from Tiago
Posted: August 26, 2013 at 14:31

Works perfectly! Thanks

Comment from alienbob
Posted: August 26, 2013 at 15:21

Hi lms,

I should have mentioned that in the article… I forgot. I have updated the main article now with a section about the slackpkg blacklist file, thanks for reminding me.

Eric

Comment from alienbob
Posted: August 26, 2013 at 16:22

phenixia2003 posted a new patch on LQ which could be merged into a future version of slackpkg+, see http://www.linuxquestions.org/questions/slackware-14/slackpkg-vs-third-party-package-repository-4175427364/page9.html#post5016280

I have not checked it out yet, but will play with it when I have some time to spare.

Eric

Comment from Matteo Rossini
Posted: August 26, 2013 at 16:30

Another tip:
slackpkg+, as slackpkg, does not have the dependency support, but some repository (as slacky and other) contains that information in metadata and slackpkg store that information in its database. So by typing “slackpkg info pkgname” you can see what package you must also install.

@Niki
We thanks to you for your repositories. I just noticed that you added the MLWS repository. I will add it at next release.

Comment from Niki Kovacs
Posted: August 26, 2013 at 16:41

@Matteo (zerouno): thanks! And you’re welcome. BTW, I won’t add anything else after MLWS, be reassured. Eventually, there will be corresponding versions for 14.1 etc. but I guess the offer is pretty much complete with Server, Desktop and Workstation. As a side note: the next MLWS will be “the full monty”, whereas MLED will only target lightweight computers and thus only sport lightweight apps.

Comment from escaflown
Posted: August 26, 2013 at 23:36

Thanks lms and Eric.

Comment from Matteo Rossini
Posted: August 27, 2013 at 14:43

slackpkg+ 0.9.4 is out, but I can’t gpg-sign it now, so you can’t upgrade with “slackpkg upgrade slackpkg”; you can download it manually.

http://slakfinder.org/slackpkg+/pkg/slackpkg+-0.9.4-noarch-1mt.txz

Now you can install kde with ‘slackpkg upgrade ktown; slackpkg install ktown’, and it install the entire ktown repository.

You can also install the entire alienbob repository with “slackpkg install alienbob” :D

That version dis-allow to use the install-new command for multilib becouse install-new should be used only for slackware packages (nor patches, nor extra, nor testing packages).

You can install multilib with “slackpkg install multilib”

thanks to phenixia2003

Comment from phenixia2003
Posted: August 27, 2013 at 16:00

Hello,

@Matteo
I’m really sorry, I sent another patch for slackpk+0.9.4 which fixes the issue about aaa_elflibs-compat32 package, and a small issue when a standard directory (ie slackware,slackware64,testing,…) is passed to slackpkg install|remove|upgrade|reinstall.

http://www.linuxquestions.org/questions/slackware-14/slackpkg-vs-third-party-package-repository-4175427364/page9.html#post5016904


SeB

Comment from Matteo Rossini
Posted: August 28, 2013 at 15:25

0.9.5 released. it contains some minor fix. http://slakfinder.org/slackpkg+/pkg/slackpkg+-0.9.5-noarch-1mt.txz

Comment from gegechris99
Posted: August 28, 2013 at 22:10

Thank you Matteo (Zerouno) for this very useful tool. I use it now to update the packages I installed from alienbob repository.

And thank you Eric for sharing this tool on the Linux Blog of 2013 :)

Comment from fabio
Posted: August 29, 2013 at 00:42

thank you alien bob and thank you gentleman who contributed to this magnific piece of software.

Comment from slackalaxy
Posted: August 29, 2013 at 09:05

Thank you for the nice review! And thanks to Matteo and all the people that submitted patches and suggestions.

Comment from tallship
Posted: September 2, 2013 at 04:09

Excellence!

Meaning, “This is exillent, wonderful, and brings Slackware management to yet another level beyond sbopkg and slackpkg alone – which belies how beneficial coupling sbopkg and slackpkg into the management of Slackware systems actually is in and of itself.

I’ve been using Slackware as a rolling release for many years, almost always simply opting for installing from current, but this slackpkg+ changes the paradigm of maintaining a -current system.

Thanks to everyone who offered comments, addtional tips, and of course, alienbob himself for spawning this discussion by publishing the article in the first place!

Kindest regards,

Bradley

.

Comment from tallship
Posted: September 2, 2013 at 04:21

OH! My der again!

First, let’s s/exillent/excellent

Next, let’s not forget to thank piterpunk, the original author who so graciously created and brought slackpkg to our community in the first place – first, as a stand-alone, then for a long time afterward when Patrick added it to /extra, and finally when it found it’s way into the mainline distro itself.

If there’s one caveat that I would like to offer here, it’s that the common consensus in the community is to rely strictly upon *official* slackware packages and SBo’s, and while it is generally accepted that there are indeed *safe* third party repos like Robby’s, Eric’s, and a few others of us who are long time hardcore supporters of Slackware, it is *STILL* the responsibility of the user him/herself to ensure the integrity of his/her own respective Slackware systems and take personal responsibility for vetting ANY 3rd party repos for use in such Slackware automation products ;)

Exillent… Really Bradley? You dufus!

Comment from dave
Posted: September 11, 2013 at 11:53

I still prefer slackyd, much more slackware-style.

Comment from ZeroUno
Posted: September 11, 2013 at 12:16

slackyd is a good tool that also supports dependencies check; an advantage is that slackyd download-only the packages so you may control the installation process (with installpkg). I have given my contribution to the its development. But a disavantage of slackyd is that it does not supports multiple repository, and I never tested it with non-slacky repositories. In past I used at the same time: slackpkg for slackware update, slackyd for slacky packages and slapt-get for 4th-party repositories. The first version (0.1) of slackpkg+ supported only the slacky repository.

Comment from Ryan P.C. McQuen
Posted: September 12, 2013 at 03:17

Thank you Eric and thank you Matteo! This brings maintaining my system to a whole new level.

What a splendid tool that I would like to see included in a default install down the line!

:-0

Pingback from Administrar repositorios con slackpkg+ en Slackware Linux (ACTUALIZADO) | 51114u9… el blog!
Posted: September 19, 2013 at 06:31

[…] AlienBob publicó un artículo [enlace] en el que describe el paquete slackpkg+ [enlace] como una útil extensión de slackpkg. Alienbob […]

Comment from ZeroUno
Posted: October 16, 2013 at 13:21

slackpkg+ is 1.0 :)

Comment from alienbob
Posted: October 16, 2013 at 13:46

Cool, just in time for Slackware 14.1 :-)

Cheers, Eric

Comment from gresolio
Posted: November 2, 2013 at 17:36

Thanks, it’s really great tool :)

I have a question about “www.slackware.com/~alien/slackbuilds/”.

I add this repository to slackpkgplus.conf. There are many packages with different versions. For example:
http://www.slackware.com/~alien/slackbuilds/lua/pkg/13.37/lua-5.1.4-i486-2alien.tgz
http://www.slackware.com/~alien/slackbuilds/lua/pkg/14.0/lua-5.1.5-i486-1alien.tgz
http://www.slackware.com/~alien/slackbuilds/libreoffice/pkg/13.37/libreoffice-3.6.7-i486-1alien.txz
http://www.slackware.com/~alien/slackbuilds/libreoffice/pkg/14.0/libreoffice-4.1.3-i486-1alien.txz
etc…

Currently slackpkgplus.conf allow to configure a priorities for a same packages in different repositories (PKGS_PRIORITY). I need some filter within one repository to include only 14.0 packages.

How to make slackpkg to use only 14.0 packages from this repository and completely ignore all other (12.2, 13.1, 13.37) ? Thanks in advance.

Comment from alienbob
Posted: November 2, 2013 at 17:58

Hi,

If you look at the slackpkgplus.conf you will see the answer to your question.

Look at how the repository for “alienbob” has been defined in MIRRORPLUS:

http://taper.alienbase.nl/mirrors/people/alien/sbrepos/14.1/x86_64/

You will see the sbrepos/14.1/x86_64 at the end. This is how I make my packages available as repositories for a specific Slackware version and architecture.

The URLS http://www.slackware.com/~alien/slackbuilds/ and http://www.slackware.com/~alien/sbrepos/ are essentially the same repository, only with a different layout. The first makes it easy to download just everything for a particular program: sources and packages. The second URL is meant to be used with package managers.

You should be using http://www.slackware.com/~alien/sbrepos/14.0/x86/ for 32-bit Slackware 14.0 packages.

Eric

Comment from gresolio
Posted: November 3, 2013 at 21:29

I tried to use Linux (especially Slackware) few years ago, but it was very hard for me (my English skills were poor, it’s the main reason). Now I returned to Slackware and enjoy it :)

Obvious things can be unclear due to language barrier. That is why I started to learn English (and little bit Deutsch) more extensively.

Repository layout is very convenient. Now I understand that “sbrepos” intended for package managers. Vielen Dank

Comment from alienbob
Posted: November 3, 2013 at 21:39

Hi gresolio

I am dutch… not deutch… small difference, different country.

Eric

Comment from ZeroUno
Posted: November 11, 2013 at 15:37

slackpkg+ 1.0 stable released.

Pingback from Alien Pastures » KDE 4.11.4 for Slackware 14.1
Posted: December 4, 2013 at 15:03

[…] that you can also use slackpkg+ (the 3rd-party repository extension to slackpkg) for these upgrades if you want, it makes the […]

Comment from Thomas
Posted: December 7, 2013 at 11:18

iss this tool off a good way?? (allow32bit, greylist) …mmhhh :)

Comment from alienbob
Posted: December 7, 2013 at 13:44

Hi Thomas

As long as slackpkg+ does not change the behaviour of slackpkg itself, I am fine with enhancements that make sense.
Remember that slackpkg+ is meant to let you manage packages from 3rd party repositories. This makes your package management more complex, and a greylist helps with avoiding package clashes.
About multilib: an often-heard complaint about Slackware’s multilib add-on is that it may be easy to install but hard to manage. I think slackpkg+ does a good job of letting you manage a multilib installation without effort, thanks to the invaluable contributions from phenixia2003.

Eric

Comment from Thomas
Posted: December 7, 2013 at 19:04

yes, but slackpkg+ self iss a litte complex at this moment for me :) Absolut better is the Information over new multilib-versions from diverse packages. Before slackpkg+ i must search of the ftp mirror …. this is top now over slackpkg+ but 32bit direkt over slackpkg when multilib and other compat32-packages iss installed. OK, i must look what make this new slackpkg+ whit my System :D
Nice 2. Advent for all.

Comment from Thomas
Posted: December 8, 2013 at 10:05

A little example, why i not to have a big trust to this tool.
Today i check updates and the Tool wont upgrade dconf 0.18 … from official Slackware whit dconf 0.11 from your repository. :/

Comment from Thomas
Posted: December 8, 2013 at 10:39

the same with openbox from SBo ….. installed is 3.5.2 , will upgrade (downgrade) to 3.5.0 from your repo.

The problem with dconf is solved by remove alienbob:.* from PKGS_PRIORITY …… but why will slackpkg+ downgrade. This is not so good , at the Moment. I Think this is a Bug?

Comment from alienbob
Posted: December 8, 2013 at 13:33

Thomas

The slackpkg+ works _exactly_ as intended.

I have dconf-0.11 in my Slackware 14.0 repository, because Slackware 14.0 does not contain dconf. A dconf package was added to Slackware 14.1 and my own repository does _not_ contain a dconf package for Slackware 14.1. Check that you are actually using a repository of mine that has “14.1″ in the URL if you run Slackware 14.1

A word about the openbox “downgrade”. When you have multiple repösitories configured in slackpkg+ then the priority of those repositories is important. Slackware does not know the concept of higher and lower versions. An “upgrade” to a lower version is entirely accepted.
You are still the admin of your computer. Even (or perhaps: especially) with an automation tool like slackpkg+ it is your responsibility to check the package list before you hit the “OK” button and upgrade your packages.

Eric

Comment from Thomas
Posted: December 8, 2013 at 16:42

This is the URL in my slackpkgplus.conf

MIRRORPLUS['alienbob']=http://taper.alienbase.nl/mirrors/people/alien/sbrepos/14.1/x86_64/
MIRRORPLUS['restricted']=http://taper.alienbase.nl/mirrors/people/alien/restricted_sbrepos/14.1/x86_64/

Its wrong?

To “downgrade” Yes, i am the Admin of my PC. thats right, thats good. :) But i have think slackpkg check the Number of Version from Packages and whe its higher than upgrade.

Comment from alienbob
Posted: December 8, 2013 at 17:01

Ah… I made a mistake when I automatically added “14.1″ symlinks in my repository… I am fixing that now, so that you will not see my dconf package again for Slackware 14.1.

Slackpkg does not check package versions. The Slackware pkgtools do not check this either.
It is what I said in my previous post: Slackware does not consider version numbers when running “upgradepkg”. You can use upgradepkg to actually downgrade a package, and that is the official intended behaviour.

Eric

Comment from ZeroUno
Posted: December 9, 2013 at 08:47

In past (a near past) I added the version check to slackpkg+ (in the development version); slackpkg+ automatically _tried_ to detect the newest version and showed the package greylisted if not newer than the installed version. But in effect was not a good think. That broke the current slackware&slackpkg phylosophy, and slackpkg+ born to add thirdy party repository without invasive feature (for example the dependency check that I was tempted to add; note that you can see package dependencies with slackpkg info |grep REQUIRED ;) )

Comment from Stephan
Posted: January 5, 2014 at 10:10

Hi Eric,

just a comment: In your slackpkgplus.conf example you are missing the repo “restricted_current” in the REPOPLUS line. Is that intended and if it is intended why is it intended?

Cheers and thanks for your help

Steph

Comment from alienbob
Posted: January 5, 2014 at 13:03

Hi Stephan

The MIRRORPLUS array contains the repositories you want slackpkg to be aware of. The REPOPLUS variable defines which of these repositories you are actually going to use. So, a repository may be defined in MIRRORPLUS but not listed in REPOPLUS, that is just fine. The other way round (listed in REPOPLUS but not defined in MIRRORPLUS) will get you an error.

Bottomline, not all repositories you define in MIRRORPLUS have to appear in REPOPLUS, which is what you noticed.

Eric

Pingback from Alien Pastures » KDE 4.11.5 for Slackware 14.1
Posted: January 7, 2014 at 21:55

[…] that you can also use slackpkg+ (the 3rd-party repository extension to slackpkg) for these upgrades if you want, it makes the […]

Pingback from slackpkg option for dependencies
Posted: February 3, 2014 at 06:26

[…] to Matteo Rossini (zerouno, on Alien BOB's blog), the following works with some third party repositories using slackpkg+: […]

Pingback from kblankscrn.kss
Posted: February 3, 2014 at 22:55

[…] to experiment, then you could read a bit about slackpkg+ which is an extension to slackpkg. See http://alien.slackbook.org/blog/intr…-repositories/ which explains how slackpkg+ makes it a lot easier to maintain Slackware if you have 3rd party […]

Pingback from Alien Pastures » Chromium, LibreOffice, Pipelight, Flashplayer updates
Posted: February 25, 2014 at 22:35

[…] you are subscribed to my repository’s RSS feed or if you are using slackpkg+ to keep your Slackware system updated, you will already have noticed and are probably already using […]

Pingback from [SOLVED] slackpkg wants to downgrade KDE
Posted: March 13, 2014 at 22:00

[…] is one (good) way of doing it. Another way is described here: http://alien.slackbook.org/blog/intr…-repositories/ […]

Write a comment