[Slackbuilds-users] [RFC] Adding features to .info format.

[Petar Petrov]

since we are talking about the INFO files again, I hope you guys will
reconsider your decision and allow for having variables within the
downloads links, e.g. for the sources version...

-p

On Tue, 28 Nov 2023 at 11:47, Lockywolf
<for_slackbuilds-users_mlist_2023-04-21 at lockywolf.net> wrote:
>
> Hello, colleagues
>
> There have been repeated discussions about two features that the current
> .info file format is missing:
>
> 1. aarch64 architecture. If in the past slarm64 was still an unofficial
>    port, with -current it is official, and quite widely available, given
>    the number of RPi machines available.
>
> 2. urls of the form https://example.test/address/ and
>    https://example.test/address/1.json , which are either not supported
>    by wget or can be mixed with each other, if downloaded into the same
>    directory, which is especially bad with Golang and Haskell builds,
>    which have many package-components, called 1.json.
>
> To address this issue, I propose a backward-compatible change to .info
> files format.
>
> 1. add DOWNLOAD_AARCH64 and DOWNLOAD_X86, a space-separated
>    bash-string-list, identical in function to DOWNLOAD and
>    DOWNLOAD_X86_64
>
> 2. add DOWNLOAD_NAME, DOWNLOAD_X86_64_NAME, DOWNLOAD_AARCH64_NAME, and
>    DOWNLOAD_X86_NAME, space-separated _optional_ strings, which, if
>    present, specify what the results of download should be named. If
>    they are absent, current logic is not changed.
>
> Please, consider the upsides and downsides of this RFC.
>
> --
> Your sincerely,
> Vladimir Nikishkin (MiEr, lockywolf)
> (Laptop)
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>