LinuxQuestions.org - slackpkg vs. third-party package repository

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - slackpkg vs. third-party package repository (https://www.linuxquestions.org/questions/slackware-14/slackpkg-vs-third-party-package-repository-4175427364/)

http://taper.alienbase.nl/mirrors/al...urrent/latest/

now you can upgrade Slackware-current with 4.11 KDE;)

Yes, that is why I created those "latest" symlinks. The URLs http://taper.alienbase.nl/mirrors/al...urrent/latest/ and http://taper.alienbase.nl/mirrors/al...e/14.0/latest/ (and in future http://taper.alienbase.nl/mirrors/al...e/14.1/latest/) will alwys point to the most recent KDE I have available for that particular Slackware release.
I am using it in combination with slackpkg+ myself, here. Works like a charm!

Eric

Quote:

Originally Posted by Alien Bob (Post 5009723)

by the way. slackpkg+ won't install packages that are new i diference with 4.10.5. They are listed as uninstalled and need to be installed by hand.

Quote:

Originally Posted by Raveriux (Post 5009730)

by the way. slackpkg+ won't install packages that are new i diference with 4.10.5. They are listed as uninstalled and need to be installed by hand.

in slackpkgplus.conf:
PKGS_PRIORITY=( alienkde:.* )
MIRRORPLUS['alienkde']=http://taper.alienbase.nl/mirrors/alien-kde/current/latest/x86_64/

next launch

slackpkg update
slackpkg install kde
slackpkg upgrade-all

edit: add
slackpkg remove kdeadmin-4 kdenetwork-4 kdesdk-4 kdetoys-4

Hello,

I have some new code for slackpkg+ (ver 0.9.3). You will find it in attachment as a patch.

If you want to test it and you're not used to use patches, then : 1) download the attached patch, and 2) apply it as below :

Code:

$ su

$ cd /usr/libexec/slackpkg/functions.d

$ patch -p0</path/to/slackpkgplus-0.9.3.patch.txt

Here is a summary of what's the new code adds and fixes :

1. Fix a small issue when a pattern is used multiple times in argument of install/upgrade. Here is an example of this issue :

Code:

$ slackpkg dialog=off install ffmpeg alienbob:ffmpeg slacky:ffmpeg Looking for ffmpeg ffmpeg ffmpeg in package list. Please wait... DONE ffmpeg-1.2-x86_64-1alien.txz gst-ffmpeg-0.10.13-x86_64-2sl.txz gst-plugins-ffmpeg-0.10.13-x86_64-2alien.tgz ffmpeg-1.2-x86_64-1alien.txz gst-ffmpeg-0.10.13-x86_64-2sl.txz gst-plugins-ffmpeg-0.10.13-x86_64-2alien.tgz ffmpeg-1.2-x86_64-1alien.txz gst-ffmpeg-0.10.13-x86_64-2sl.txz gst-plugins-ffmpeg-0.10.13-x86_64-2alien.tgz Total package(s): 9

2. Fix a small bug in install/upgrade regarding the enhanced priority rules which are inserted into the variable PRIORITY in the reverse order. For instance, if you issue "slackpkg install r1:foo r2:bar", then PRIORITY is set to ( r2:bar r1:foo ... ) instead of ( r1:foo r2:bar ).

3. Fix a small bug in search which leads to wrong information about possible upgrade. For instance, on a testing Slackware64/multilib "slackpkg search qt" outputs the following (errors in red) :

Code:

[ Status ] [ Repository ] [ Package ] installed kdevelop-pg-qt-1.0.0-x86_64-1 installed perlqt-4.8.5-x86_64-1 installed qtruby-4.8.5-x86_64-1 installed smokeqt-4.8.5-x86_64-1 installed libdbusmenu-qt-0.9.2-x86_64-2 installed polkit-qt-1-0.103.0-x86_64-1 upgrade qt-4.8.2-x86_64-4 qt-compat32-4.8.2-x86_64-4compat32 --> qt-4.8.2-x86_64-4 installed qtscriptgenerator-0.2.0-x86_64-1 uninstalled alienbob razor-qt-0.5.2-x86_64-1alien uninstalled slacky qtcurve-gtk2-1.8.16-x86_64-1sl uninstalled slacky razorqt-0.5.2-x86_64-1sl uninstalled slacky qt3-3.3.8b-x86_64-1sl uninstalled slacky avidemux-qt4-2.5.6-x86_64-2sl uninstalled slacky qt-recordmydesktop-0.3.8-x86_64-10sl uninstalled slacky bitcoin-qt-0.7.1-x86_64-1sl uninstalled slacky qtransmission-2.75-x86_64-1sl upgrade ktown qt-4.8.2-x86_64-4 qt-compat32-4.8.2-x86_64-4compat32 --> qt-4.8.4-x86_64-5alien upgrade ktown perlqt-4.8.5-x86_64-1 --> perlqt-4.10.5-x86_64-1alien upgrade ktown qtruby-4.8.5-x86_64-1 --> qtruby-4.10.5-x86_64-1alien upgrade ktown smokeqt-4.8.5-x86_64-1 --> smokeqt-4.10.5-x86_64-1alien installed multilib qt-compat32-4.8.2-x86_64-4compat32

4. Improved slackpkg+ so that it is now possible to install/upgrade/reinstall/remove all the packages from a given repository using the syntax :

Code:

slackpkg install|upgrade|reinstall|remove <repository_name>

For instance, once you have uncommented the line "PKGS_PRIORITY=( multilib:.* ) in your /etc/slackpkg/slackpkgplus.conf, you can turn your pure 64-bit version of Slackware into Slackware64/multilib with the commands below :

Code:

$ slackpkg upgrade gcc glibc (or slackpkg upgrade-all) $ slackpkg install multilib

If you want to upgrade only the multilib packages, you can issue the command :

Code:

$ slackpkg upgrade multilib

When new packages have been added to the multilib, or in case some of the multilib packages are missing, you can grab them using the command :

Code:

$ slackpkg install multilib

If you want to fully reinstall the multilib, you will issue the command :

Code:

$ slackpkg reinstall multilib

If you no longer need the multilib and want to return to true 64-bit, you can now proceed as below :

+ Comment the line "PKGS_PRIORITY=( multilib:.* ) in your /etc/slackpkg/slackpkgplus.conf

+ remove the multilib packages :

Code:

$ slackpkg remove multilib

+ reinstall the pure 64-bit gcc/glibc :

Code:

$ slackpkg upgrade gcc glibc

Note:
To prevent system breakage, slackpkg+ automatically blacklist the packages gcc/glibc when the repository passed to "remove" contains the string "multilib"

IMPORTANT:

For consistency purpose, the code to install missing compat32 packages using "slackpkg install-new" should be removed. Indeed, install-new is not designed for this as stated in slackpkg documentation :

Quote:

install-new
This action installs any new packages that are added to the official Slackware package set. Run this if you are upgrading your system to
another Slackware version or if you are using -current. If you want to install all uninstalled Slackware packages onto your system, use
the following command instead of the install-new action:

# slackpkg install slackware

The improvement #4 fixes this inconsistency, and user can now install the missing/new compat32 packages with "slackpkg install multilib". However, I didn't remove the "install-new" code because there's an issue with the package aaa_elflibs-compat32 which can not be installed (nor upgraded/reinstalled/removed) using "slackpkg install|upgrade|reinstall|remove multilib" because slackpkg's blacklist contains the pattern aaa_elflibs. If anybody have an idea to fix that issue, this would be great.

Hope this helps.

Cheers.

--
SeB

it's a good patch, thankyou. Unfortunatley I've not a Slackware pc this week so I can release next version not before than 2/september

0.9.4 released, but you must download it manually (I can't generate metadata files)

Hello,

Quote:

Originally Posted by zerouno (Post 5016868)

0.9.4 released, but you must download it manually (I can't generate metadata files)

Thanks for the update ... But I have some new code for you :D

I had an idea to fix the issue I was talking about at the end of my previous post (ie silent exclusion of aaa-elflibs-compat32). As a consequence, I removed the code to install missing compat32 packages using "slackpkg install-new".

Furthermore, I also fixed a small issue about packages selection when one of the standard slackware's directories (ie slackware, slackware64, testing,extra, patches) is passed in argument of "slackpkg install|upgrade|remove|reinstall".

For instance, if slackpkg+ is configured with the repositories "multilib" and "microlinux", running "slackpkg install slackware64" leads to select packages from slackware64 directory, but also packages from "multilib" and "microlinux" repositories, because packages from these repositories are stored in directories whose names include the word "slackware64".

In attachment, you will find the patch for slackpkg+ 0.9.4.

Cheers

--
SeB

Hello

it's very nice tool indeed! However, if i package something myself and it happens to be a newer version than its equivalent on the repos, it shows the repo version as an update.
i.e. i have libreoffice 4.1 and it prompts me to "update" to 4.0.5.

Is it possible to circumvent this behavior somehow?

In slackware64-current my config is:
PKGS_PRIORITY=( multilib:.* )
REPOPLUS=( slackpkgplus multilib restricted_current restricted alienbob_current alienbob slacky )

so if i'm not mistaken, the priority is: multilib packages, then slackware packages, then the repoplus vector in order.

@kfn: Use a tag for your own packages, e.g. suppose you called your package libreoffice-4.1-x86_64-1kfn.txz. You could then add '[0-9]+kfn' to /etc/slackpkg/blacklist and your package would not be prompted for upgrade.

If you do that though, bear in mind that you will not be prompted for updates as long as it remains blacklisted, even if one the repos starts to have a newer version in the future. Whilst blacklisted it is entirely up to you to manually manage updates for that package, should you want them. This may be obvious but I thought I would state it nonetheless, just in case it wasn't. ;)

Quote:

Originally Posted by ruario (Post 5017231)

@kfn: Use a tag for your own packages, e.g. suppose you called your package libreoffice-4.1-x86_64-1kfn.txz. You could then add '[0-9]+kfn' to /etc/slackpkg/slackpkg.conf and your package would not be prompted for upgrade.

Should that not be:

add '[0-9]+kfn' to etc/slackpkg/blacklist

Hello, I have two questions:

Is there any change that slackpkg+ will be added to the slackware tree?
Are threre a repository for SBo, or the idea to add one?

Quote:

Originally Posted by mlpa (Post 5017514)

Hello, I have two questions:

Is there any change that slackpkg+ will be added to the slackware tree?
Are threre a repository for SBo, or the idea to add one?

As SBo does not contain packages, but scripts for making packages, repository for SBo have no sence. For SBo packages use a sbopkg tool.