[Slackbuilds-users] separating source archives and SlackBuilds

Tim Dickson dickson.tim at googlemail.com
Sat May 22 21:39:53 UTC 2021

Unfortunately it doesn't quite work. A number of the source files have 
the same name, even though they are different. Especially for 
multi-versions available, such as various versions of jdk.
On the other hand, if you use sbopkg for creating packages, it already 
has a default location for source, /var/cache/sbopkg/  and that is 
checked first before the source url's, to save re-downloading the same 
files. You might want to try it, as it sounds like the behaviour you are 
looking for. It still suffers from the issue mentioned, but as it checks 
md5sums, it offers to download the correct source, which is useful.
regards, Tim

On 22/05/2021 21:19, Thomas Morper wrote:
> Hello there!
> There's a certain feature in FreeBSD ports that I think I'd like to have
> in SlackBuilds, too, and I want to know what you think about it:
> FreeBSD ports keep all source archives in the /usr/ports/distfiles folder
> while SlackBuilds expect the source archive in the same folder as the
> SlackBuld itself.
> With a simple "DISTFILES=${DISTFILES:-$CWD}" and "tar xvf $DISTFILES/..."
> rather than "tar xvf $CWD/..." in the template we could have both ways.
> The reason for keeping it the way it is: simplicity.
> The reason for having a separate distfiles folder: you can keep as many
> source archive versions around as you want without affecting the way you
> work with the SlackBuilds directory tree, e.g. always using a pristine and
> possibly read-only copy, or going all-in on git without ever accidentally
> adding and comitting the LibreOffice tar ball.
> Would this be desirable and feasible?
> Cheers!

This email has been checked for viruses by AVG.

More information about the SlackBuilds-users mailing list