[Slackbuilds-users] RFC: more variables

[Petar Petrov]

well,

I have seen a DOCS= variable in some SlackBuilds. As for the benefits
of introducing the variables you propose -- will this change make the
scripts look simpler? I am really asking, not arguing :) I usually
just remove the corresponding blocks of text if they are not needed. I
do not mind if templates are changed following your idea, but I will
not be updating my scripts just for that.

-petar

2016-08-14 8:29 GMT+03:00 Klaatu <klaatu at member.fsf.org>:
> It seems like the 14.2 rush has slowed down a little, so I want to take
> an opportunity to propose a change to the SBo templates. This probably
> would have better been timed BEFORE 14.2 was released, but it didn't
> occur to me until I was rebuilding some systems to update everything to 14.2
>
> My idea:
>
> We use variables at the head of the SlackBuild scripts for things like
> program name, version number, arch, and so on. I think it would be nice
> to also variable-ize these values:
>
> Doc path (DOCDIR)
> Man path (MANDIR)
> Info path (INFODIR)
>
> Benefits: A SlackBuild can be quickly and reliably modified by targeting
> these variables either through env setting or with sed. Currently the
> destination of these values is hardcoded in the lower half of a
> SlackBuild file (when moving docemention, or gzipping man pages).
>
> Cost/Drawbacks: None? A rotential drawback is a sense of obligation to
> change current build scripts to conform to new template, but I'm
> proposing more a shift in habit than a complete immediate overhaul.
>
> What do other people think? Does this sound reasonable, even helpful?
>
> Cheers,
>
> - Klaatu
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>