<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Should programs which are only available in binary form also be
named *-bin?<br>
<br>
Some examples: resilio-sync, stm32cubeide, stm32cubeprog, teams
and others.<br>
</p>
<div class="moz-cite-prefix">Op 10-03-2025 om 14:21 schreef
<a class="moz-txt-link-abbreviated" href="mailto:phalange@komputermatrix.com">phalange@komputermatrix.com</a>:<br>
</div>
<blockquote type="cite"
cite="mid:dfa78a7b6ef61f6e067de5252769d2d2@komputermatrix.com">On
2025-03-10 04:11, thinkunix via SlackBuilds-users wrote:
<br>
<blockquote type="cite">B. Watson wrote:
<br>
<blockquote type="cite">
<br>
<br>
On Tue, 4 Mar 2025, fsLeg wrote:
<br>
<blockquote type="cite">
<br>
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?
<br>
</blockquote>
<br>
Good question. I might not bother with the -bin in that case.
<br>
</blockquote>
<br>
Wouldn't it be better to always use the "-bin" for binary
repacks?
<br>
Then if the source is eventually released, you won't have naming
<br>
issues. The non"-bin" version is built from source; the "-bin"
is
<br>
a binary repack.
<br>
_______________________________________________
<br>
SlackBuilds-users mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users">https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a>
<br>
Archives -
<a class="moz-txt-link-freetext" href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a>
<br>
FAQ - <a class="moz-txt-link-freetext" href="https://slackbuilds.org/faq/">https://slackbuilds.org/faq/</a>
<br>
</blockquote>
<br>
I share this view; I maintain a couple binaries and I'd be happy
to rename them *-bin.
<br>
<br>
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).
<br>
_______________________________________________
<br>
SlackBuilds-users mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users">https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a>
<br>
Archives -
<a class="moz-txt-link-freetext" href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a>
<br>
FAQ - <a class="moz-txt-link-freetext" href="https://slackbuilds.org/faq/">https://slackbuilds.org/faq/</a>
<br>
<br>
</blockquote>
</body>
</html>