[SOLVED] [SUGGESTION]

samac · 01-19-2014, 06:18 AM

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

samac

Alien Bob · 01-19-2014, 06:21 AM

There are no "patches" in slackware-current.

Eric

samac · 01-19-2014, 07:49 AM

Eric

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

Alien Bob · 01-19-2014, 08:18 AM

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.

Eric

rob.rice · 01-19-2014, 10:50 AM

Quote:

Originally Posted by samac

Eric

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

it would save nothing

samac · 01-19-2014, 11:56 AM

@ Alien Bob

You're right, I was only considering part of the problem. Consider this suggestion as sent to /dev/null.

@ rob.rice

Not patches to the source code patches as in the directory.

samac

Alien Bob · 01-19-2014, 12:58 PM

Quote:

Originally Posted by rob.rice

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.

Eric