LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 08-08-2014, 01:57 PM   #1
atelszewski
Member
 
Registered: Aug 2007
Distribution: Slackware
Posts: 948

Rep: Reputation: Disabled
sbopkg blacklist package by given version (proposal)


Hi,

I know that blacklisting in sbopkg was discussed on its mailing list and good reasons were given not to include the package blacklisting possibility, but what I'm thinking of is a slightly different idea.

What I mean is to add the possibility to blacklist an exact version of specified package, so it does not show up in the Updates. If there is a newer version or anything else changes in the upstream (slackbuilds.org) package name, then the package would reappear in the Updates.

This way it would be possible to watch for updates, yet keep the sbopkg silent when the upstream name matches the blacklisted one.

The reason behind my idea is that, sometimes the changes to the upstream SlackBuilds are kinda cosmetic, like updating the README or it is a change that I know is of no help for me. And I'm fine with rebuilding the package, for the sake of keeping Updates clean, if the package is relatively small. But when it comes to for example qemu or webkit I'm always postponing it as long as I can, but I know they are lurking somewhere in the darkness...

What do you think?

EDIT:
OK, due to some mental problems I though that the cosmetic change to the upstream SlackBuild tarball would bump the BUILD part of the package name, which apparently is not the case. Anyway, maybe the idea is still valid if you don't want to rebuild a huge package just because a single line in a small C file has been changed and you know you don't care?

--
Best regards,
Andrzej Telszewski

Last edited by atelszewski; 08-08-2014 at 02:50 PM.
 
Old 08-09-2014, 11:35 PM   #2
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 4,764

Rep: Reputation: 1862Reputation: 1862Reputation: 1862Reputation: 1862Reputation: 1862Reputation: 1862Reputation: 1862Reputation: 1862Reputation: 1862Reputation: 1862Reputation: 1862
IMO: the decision to update or not should come from the user, not from the tool since the tool has done it's job very well.

The BUILD bump will happen if there's a change in the resulting packages.
 
Old 08-11-2014, 08:45 AM   #3
atelszewski
Member
 
Registered: Aug 2007
Distribution: Slackware
Posts: 948

Original Poster
Rep: Reputation: Disabled
Hi,

Quote:
the tool has done it's job very well.
Indeed, I guess everyone who has come across the slackbuilds.org and sbopkg has loved the duet at first sight

Quote:
the decision to update or not should come from the user, not from the tool
I do agree, but I think that instructing the tool what to do is your decision.

My approach is simple: allow blacklisting given package version not to show up in the Updates. It will still show up in the Search, you can still rebuild it and what is the most important part, you will be noticed whenever the upstream updates the SlackBuild.

--
Best regards,
Andrzej Telszewski
 
Old 08-11-2014, 09:23 AM   #4
55020
Senior Member
 
Registered: Sep 2009
Location: Yorks. W.R. 167397
Distribution: Slackware
Posts: 1,307
Blog Entries: 4

Rep: Reputation: Disabled
You might want to have a look at slackrepo. You can create a hintfile (similar to .info or sbopkg .options) that contains 'SKIP="any message you want to display"'. I used this for skipping webkitgtk updates when I was writing and testing slackrepo.

It's not perfect for your use case at the moment, as it will always display a message that the package has been skipped even when the package already exists and is up to date, but I will improve that situation in the next release. (It already does something similar for packages that need manual downloading, such as jdk.) Thanks for the idea!

I don't think that the highly automatic updates in slackrepo are a loss of control for the user, for two reasons: (1) it has a '--dry-run' control argument, and (2) it will soon have a new feature for automatically archiving updated packages and for restoring them on request.

The other thing that you might not like is that slackrepo will always do an update if git has changed, even if it is only a change to README or the maintainer, and any depending packages will be rebuilt. I have been thinking about whether to add an option for relaxing this behaviour, but at the moment it is "Better safe than sorry".

Also, it will *always* increase the BUILD for updates and rebuilds. This ensures that the repository will work with slackpkg+.

I don't want to bash sbopkg, it is now almost perfect for its purpose, but we also need to experiment with new ideas, and if some of those new ideas are good, I would consider it an honour if those ideas were "stolen"
 
Old 08-11-2014, 10:30 AM   #5
atelszewski
Member
 
Registered: Aug 2007
Distribution: Slackware
Posts: 948

Original Poster
Rep: Reputation: Disabled
Hi,

@55020 thanks for your suggestion on slackrepo. But I'm not yet ready to move to something new, so I'll stay in the sbopkg camp The point is, sbopkg suits me very well, the blacklisting is the only thing I'm wishing for at the moment. Although it might require quite some investigation, I might jump into the source code one day and add the functionality if the upstream does not. Nobody is to be blamed, sbopkg is stable and works well, my proposal is rather obvious, but surely needs time for proper incorporation.

--
Best regards,
Andrzej Telszewski
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Upgrading Apache 2.2.16 (package version) to the latest version 2.2.26 (compiled vers Renaud06 Debian 8 11-27-2013 06:59 PM
Blacklist package group from slackpkg Phorize Slackware 2 08-19-2013 04:34 AM
A proposal regarding the _registration_ of package dependencies by Pkgtools Darth Vader Slackware 13 07-13-2011 05:01 AM
A proposal: Classification of package install asou Slackware 11 07-24-2009 01:21 PM
LXer: Sbopkg provides seamless package repository integration for Slackware LXer Syndicated Linux News 0 10-02-2008 07:10 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 10:29 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration