[Slackbuilds-users] naming conventions (compiled & binary) (was Re: LibreOffice vs libreoffice (confusing, too vague))

Christoph Willing chris.willing at linux.com
Sat Apr 8 10:48:39 UTC 2023


On 8/4/23 20:10, dchmelik at gmail.com wrote:
> On 4/8/23 2:29 AM, Christoph Willing wrote:
>> On 8/4/23 16:53, B. Watson wrote:
>>>
>>>
>>> On Sat, 8 Apr 2023, Christoph Willing wrote:
>>>
>>>> Perhaps those *-bin SlackBuilds should have followed the existing 
>>>> convention provided 2 years earlier by Libreoffice/libreoffice - 
>>>> also Blender/blender 3 years earlier in Aug 2015.
>>>
>>> Gods, no. We'd have had even more confusion. Just because it was done
>>> doesn't make it a good idea to keep doing...
>>>
>>> I think having 2 builds with names that only differ in capitalization
>>> is a horrible idea. I'd even say it'd be a good idea to rename
>>> LibreOffice to libreoffice-bin and Blender to blender-bin.
>>
>> It was a joke.
>>
>> However the change would be:
>>    libreoffice -> libreoffice-bin and LibreOffice -> libreoffice
>>    blender -> blender-bin         and Blender -> blender
>>
>> since the currently capitalized versions build from source and 
>> uncapitalized versions repackage binaries.
> 
> Aren't there still many capitalized SlackBuilds that build from source 
> without each matching a SlackBuild that does a binary?  I thought it'd 
> be up to upstream and maintainers what capitalization to use... not that 
> I do any that use binaries.


Yes there may be many SlackBuilds like that. As you say, it's up to 
upstream and maintainers what capitalization to use. I was referring 
only to the LibreOffice and Blender SlackBuilds which I maintain.

chris




More information about the SlackBuilds-users mailing list