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.
Unfortunatly (???) I'm in vacation and I've not my pc. I'm releasing slackpkg+ 0.9.4 and 0.9.5 from a microsoft pc () so I cannot generate the needed metadata.
I will update repository next monday.
@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.
That's one way to go for sure. However, apart from the fact that you would have to manually check for updates as you said, the potential "upgrade" could also happen with newer packages from other sources too (outside of slackpkg+ repos), not only self-packaged ones. So all have to be blacklisted and manually checked later.
So a more proactive behavior sounds good to me: if in case a newer package is not blacklisted and is not in the default repos, then slackpkg+ instead of putting it in the upgrade list, can just give a notification/warning like "Installed version is newer than the repo version"; i think sbopkg does something similar.
That's one way to go for sure. However, apart from the fact that you would have to manually check for updates as you said
Well, you already do that when you package your own software
Quote:
Originally Posted by kfn
So a more proactive behavior sounds good to me: if in case a newer package is not blacklisted and is not in the default repos, then slackpkg+ instead of putting it in the upgrade list, can just give a notification/warning like "Installed version is newer than the repo version"; i think sbopkg does something similar.
Or...
...you could have a local repository with your own packages and add it in the appropriate priority list to slackpkg+
You could use AlienBOB's gen_repos_files.sh script to make a slackpkg+ compatible repository.
Nice to see slackpkg+ on sourceforge. Moreover, It's a good idea to have the repository name beside of the package. I have played a bit with this and I found a tiny annoying bug (pointed by the red debug lines) :
Code:
slackpkg install ffmpeg vlc
Looking for ffmpeg vlc in package list. Please wait... DONE
(DEBUG) found ffmpeg-1.2-x86_64-1alien.txz in repo alienbob
restricted
(DEBUG) found gst-ffmpeg-0.10.13-x86_64-2sl.txz in repo slacky
(DEBUG) found gst-plugins-ffmpeg-0.10.13-x86_64-2alien.tgz in repo alienbob
(DEBUG) found npapi-vlc-20130408-x86_64-1alien.txz in repo alienbob
restricted
(DEBUG) found phonon-vlc-0.6.0-x86_64-1alien.txz in repo alienbob
(DEBUG) found vlc-2.0.8-x86_64-1alien.txz in repo alienbob
restricted
==============================================================================
WARNING! WARNING! WARNING! WARNING! WARNING!
==============================================================================
One or more errors occurred while slackpkg was running:
DIALOG ERROR:
-------------
xargs: unmatched double quote; by default quotes are special to xargs unless you use the -0 option
Error: Expected at least 7 tokens for --checklist, have 5.
Use --help to list options.
-------------
If you want to continue using slackpkg, disable the DIALOG option in
/etc/slackpkg/slackpkg.conf and try again.
Help us to make slackpkg a better tool - report bugs to the slackpkg
developers
==============================================================================
This bug only occurs when a package can be found in more than one repository, like vlc and ffmpeg which are in alienbob and restricted repositories.
Uploaded a new version on sourceforge. Is a 'snapshot' version becouse it need testing. For security it is not available with slackpkg upgrade slackpkg+
It add a new feature.
You can install/upgrade packages from file without the needed metadata.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
) so I cannot generate the needed metadata.
