I do not intend to sound nagging, but why not implement such a feature in order to make maintainers' job easier?
-petar On Sat, 25 Feb 2023 at 07:03, B. Watson <[email protected]> wrote: > > > Maintainers, please don't use $PRGNAM, $VERSION, etc in .info file keys. > > Examples: > > DOWNLOAD="https://github.com/kovmir/$PRGNAM/archive/v$VERSION/$PRGNAM-$VERSION.tar.gz"; > > DOWNLOAD_x86_64="https://gitlab.com/api/v4/projects/24386000/packages/generic/librewolf/$VERSION-1/LibreWolf.x86_64.AppImage"; > > I know the .info file looks like valid shell script code (and it > is), but it's also used by things that aren't shells, which don't do > variable substitution. Things like, the SBo database itself, and the > sbosrcarch downloader. > > Because someone will ask... No, the guidelines on the website don't > say anything about this, but the examples clearly don't use it. It > never occurred to us that someone would do this, which is why there > hasn't been a written policy about it. > _______________________________________________ > SlackBuilds-users mailing list > [email protected] > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > _______________________________________________ SlackBuilds-users mailing list [email protected] https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
