[Slackbuilds-users] RFC: changing .SlackBuild to allow separate source tree

King Beowulf kingbeowulf at gmail.com
Wed Aug 7 15:36:39 UTC 2013

On 08/07/2013 12:29 AM, David Woodfall wrote:
> Although it seems like a good idea to add a MYSRC to the slackbuild,
> you could just as well do a ln -s /where/the/source/is/source.tar.xz .
> and then run the slackbuild.
> Either way you're typing extra bumf. It's seems much easier to me and
> do a 'source *info && wget $DOWNLOAD'
> Just my two pennies worth.
> D.

Yep, used to do that way back but got tired of creating/fixing links all
the time. The problem with 'ln -s' is when updating the slackbuild
script tree, as in a git pull from SBo or elsewhere.  It will be also a
problem when doing a git push, or, say, making a tar.gz t upload to SBo.
The link still puts a "source file" in that directory.  Instead of
dealing with the source, you have to deal with the link. Since SBo
script packages don't have links, you have to add a step each time to
create one, or make sure you don't stomp on one, when getting a fresh copy.


More information about the SlackBuilds-users mailing list