[Slackbuilds-users] Patches in `$PKG/usr/doc/$PRGNAM-$VERSION/`?

[King Beowulf]

On 08/10/2015 08:13 PM, Thomas Szteliga wrote:
> SlackBuild templates (and scripts) contain this line:
> 
> 
> ~~~~
> cat $CWD/$PRGNAM.SlackBuild \
>     > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
> ~~~~
> 
> 
> but what if a SlackBuild script requires patches applied
> during its execution. Shouldn't they be copied to
> 
> 
> 	$PKG/usr/doc/$PRGNAM-$VERSION/
> 
> as well?
> 
> 
> For example, `arj` <http://slackbuilds.org/repository/14.1/system/arj/>
> requires a lot of patches
> <http://slackbuilds.org/slackbuilds/14.1/system/arj/patches/> but the
> SlackBuild script
> <http://slackbuilds.org/slackbuilds/14.1/system/arj/arj.SlackBuild>
> still contains only:
> 
> ~~~~
> cat $CWD/$PRGNAM.SlackBuild \
>     > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
> ~~~~
> 
> 
> leaving the patches out.
> 
> 

my 2 cents:  The patches, and the slackbuild script itself, is only
useful if you want to build the package. Neither has any compelling need
to be in /usr/doc, and are perfectly useless by themselves.  Any patches
needed to compile the source should, nay must, be included in the
$PRGNAM.tar.gz tar ball.  Including the tar ball in /usr/doc is just
redundant: this is easily available on SBo, SBo git and any number of
mirrors.  Besides, any user will ALREADY have these files downloaded.

For those who say "hard drive space is cheap:"  Do no assume others'
financial condition or hardware availability.  Also, wasting space is
just inefficient and lazy.

-Ed


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150811/c2082476/attachment.asc>