[Slackbuilds-users] naming conventions

[kind.note8582 at fastmail.com]

I’d like to discuss package naming conventions, using kubectl as an example. 
The current package uses a precompiled version of kubectl. 
I’ve created a new SlackBuild that compiles it from source, resulting in a much smaller binary. 
This got me thinking..... why don’t we adopt a consistent naming approach like this:

     - kubectl.SlackBuild (compiles from source)
     - kubectl-bin.SlackBuild (repacks prebuilt binaries)

What do you think?

--
BR,
r1w1s1