[SOLVED] [SUGGESTION] - Small modification to slackpkg
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.
I use the stable version of Slackware rather than current, and all update are put in patches.
In slackpkg.conf I have changed this section to read
Quote:
# PRIORITY sets the download priority. slackpkg will try to found the
# package first in the first value, then the second one, through all
# values in list.
#
# Default value: patches %PKGMAIN extra pasture testing
PRIORITY=( patches )
This works fine for stable but would not work for current. It also saves time and bandwidth whilst doing a slackpkg update.
My suggestion is this:
Would it be possible to do a conditional statement that says
if slackware current
then
priority = %PKGMAIN extra pasture testing
else
priority = patches
fi
Modified per your comment. I still think it would be a good modification for those that use stable versions of slackware, as it would save them both time and bandwidth.
You are considering only a limoted use-case samac: using slackpkg to keep an already installed Slackware up to date with patches.
However, slacpkg is also used for installing packages from the core repository. Something like "slackpkg install partitionmanager", or even "slackpkg install kde" would not work if you only point slackpkg to the /patches directory.
Modified per your comment. I still think it would be a good modification for those that use stable versions of slackware, as it would save them both time and bandwidth.
samac
the patches are applied to SOURCE CODE EVERY THING PATCHED WOULD NEED TO BE REBUILT !!!!
source code can be as much as 10 times larger than executablies so that would use more bandwidth
building from source tacks about 1000 times more time than installing a package
the patches are applied to SOURCE CODE EVERY THING PATCHED WOULD NEED TO BE REBUILT !!!!
source code can be as much as 10 times larger than executablies so that would use more bandwidth
building from source tacks about 1000 times more time than installing a package
it would save nothing
Perhaps you were a bit too quick in answering here... Apparently you have no idea what we are talking about.
The /patches directory in Slackware contains packages which have been upgraded after an official release, mostly security fixes. This has nothing to do with patches to source code.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
