[Slackbuilds-users] separating source archives and SlackBuilds

Thomas Morper thomas at beingboiled.info
Sat May 22 20:19:43 UTC 2021

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?



More information about the SlackBuilds-users mailing list