[Slackbuilds-users] naming conventions

[kind.note8582 at fastmail.com]

Nice! thank you all for the feedback, I will create PR today.


---
BR
r1w1s1(Ricardson)

On Sun, Mar 9, 2025, at 12:33 AM, Willy Sudiarto Raharjo wrote:
>>  >why don’t we adopt a consistent naming approach like this:
>>  >
>>  >       - kubectl.SlackBuild (compiles from source)
>>  >       - kubectl-bin.SlackBuild (repacks prebuilt binaries)
>> 
>> This question was actually raised a few days ago in a thread about a 
>> proposed SlackBuild template for packaging pre-built binaries. It also 
>> proposed to name scripts for repackaging software as *-bin, and in the 
>> following discussion I felt that the consensus was to use exactly that 
>> naming scheme for SlackBuilds, except for cases when repackaging a 
>> binary is the only SBo-compatible way (like proprietary software).
>> 
>> So you should ask the current maintainer of kubectl to rename the 
>> SlackBuild to kubectl-bin or even remove it altogether if building from 
>> source doesn't require many dependencies and not resource-intensive.
>
> IMHO, we don't really need a spesific template for pre-built binaries, 
> since it's just a matter of packaging. We can just use the existing 
> templates and adjust it with the project we are trying to package.
> Template is useful when there's a spesific ways of packaging projects 
> using different build tools, like rust, go, python, perl, etc.
> I agree with *-bin naming thing. It's consistent with what we have 
> currently in our repo.
>
> as for kubectl, i didn't know the situation when i took over kubectl 
> from Dimitris and pushed the public update. I saw he was trying to 
> remove it, so i took over because i used it. If r1w1s1 wants to provide 
> a script for building it from source, feel free to send PR.
>
> I will submit a new script kubectl-bin for this purpose.
>
> During normal cycle like nowadays, renaming is two-way process: Add new 
> script and remove old one. It has to be done manually since it need to 
> be populated in the database.
>
> For mass renames, i would suggest to do it during development for new 
> SBo repo for next Slackware release. Since everything is not yet 
> populated in the database, we can do "wild" things in the repo: adding 
> new scripts, renames, delete broken scripts, etc.
>
>
> -- 
> Willy Sudiarto Raharjo
>
> _______________________________________________
> 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/
>
>
> Attachments:
> * OpenPGP_signature.asc