Mailinglist Archive: opensuse-packaging (127 mails)

< Previous Next >
Re: [opensuse-packaging] Re: Poll about Url vs URL in RPM preamble
On Thursday 2017-08-10 20:10, Jan Ritzerfeld wrote:

Am Mittwoch, 9. August 2017, 22:56:16 CEST schrieb Jan Engelhardt:
[...] The specfiles on the other hand have their tags
*consistently* camelcased from the words they were formed from, like
{build architectures -> BuildArch}, {automatic requires and provides ->
AutoReqProv}, etc. Except for {uniform resource location -> Url} which
is the odd bit.

As I already told you, "Url" is perfect upper camel case! See
https://google.github.io/styleguide/javaguide.html#s5.3-camel-case

"url" is not a word in a linguistic sense, but an acronym; as for the scope of
Google's document, URL is in the same class as "IPv6", and so their
recommendations don't even apply, the result of which can be seen in, for
example, the Chromium source code - which is not Java, but let's use it for the
sake of argument - where they just use any casing they liked at the particular
moment.

rpm has had its own style for well over 12 years. Its documentation and
lots and lots of spec files from other distributions that were not
subject to format_spec_file have all come to terms to use URL. The
ruleset can be expressed as: lc, ucfirst, join, and *trim* (the latter
of which is unheard of in the Goog/MS doc). And with that, we get, for
the examples mentioned earlier:

. automatic requires and provides -> AutomaticRequiresAndProvides -> AutoReqProv
. uniform resource location -> UniformResourceLocation -> URL


[In other news, perhaps this is the time to patch rpm and rename it to
Homepage:, resolving the issue without having to argue about acronym
renditions.]
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx

< Previous Next >