[Slackbuilds-users] [RFC] a binary repack SlackBuild template.

[Spycrowsoft]

Should programs which are only available in binary form also be named *-bin?

Some examples: resilio-sync, stm32cubeide, stm32cubeprog, teams and others.

Op 10-03-2025 om 14:21 schreef phalange at komputermatrix.com:
> On 2025-03-10 04:11, thinkunix via SlackBuilds-users wrote:
>> B. Watson wrote:
>>>
>>>
>>> On Tue, 4 Mar 2025, fsLeg wrote:
>>>>
>>>> What about proprietary software? It's only distributed as pre-built 
>>>> binaries (like mentioned discord, also saflashplayer). Do such 
>>>> packages need to be named *-bin?
>>>
>>> Good question. I might not bother with the -bin in that case.
>>
>> Wouldn't it be better to always use the "-bin" for binary repacks?
>> Then if the source is eventually released, you won't have naming
>> issues.  The non"-bin" version is built from source; the "-bin" is
>> a binary repack.
>> _______________________________________________
>> 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/
>
> I share this view; I maintain a couple binaries and I'd be happy to 
> rename them *-bin.
>
> IMHO it's easier to have a rule than a case-by-case evaluation (i.e., 
> checking is there, could there be a source code build).
> _______________________________________________
> 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/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250312/d49194d1/attachment.htm>