KDE Discover binary & library names

[Matthias Klumpp]

2016-01-07 18:06 GMT+01:00 Jonathan Riddell <jr at jriddell.org>:
> On Thu, Jan 07, 2016 at 05:59:50PM +0100, Matthias Klumpp wrote:
>> So, possible solutions would be, for the binary:
>>  1) Keep the name "muon-discover", although there is no connection to
>> Muon anymore
>>  2) Use "plasma-discover"
>>  3) Use "kde-discover"
>>  4) Use "kdiscover"
>>  5) ${ANY_OTHER_NAME}
>
> Not 4! Please anything but 4! :)

:D - I figured as much ^^
In that case, maybe "plasma-discover" makes the most sense, I guess
(since it's not only about exploring stuff the KDE community made, and
because discover is technically part of Plasma).


>> For the library:
>>  A) Keep the name and make it a private library, by moving it out of
>> /usr/lib and into e.g. /usr/lib/kde-discover. This would make the lib
>> only accessible to Discover itself, other tools wouldn't find it.
>>
>>  B) Change the name to something like "libkdiscover"
>>  C) ${ANY_OTHER:NAME}
>
> Oh dear gods not B!

For that, I think libkdiscover actually makes sense (I hate long
library names, like libplasmadiscover would be...). If really nothing
except for Discover-components is going to link against that library,
making it private in a /usr/lib/<triplet>/plasma-discover subdirectory
makes the most sense, I guess.

>> Keep in mind that this is only about binary and library names (and
>> probably the name of the release tarball?), the name of the
>> application remains what it is.
>> Aleix and I briefly discussed this on a few occasions last year, but
>> would like some feedback from more people on it.
>
> Thanks for bringing this up, I'm fine with any of 1,2 or 3 and would sync the tar to follow that.

Neat, thanks for that in advance!
Cheers,
    Matthias (who wants to see an updated Discover in Debian soon ^^)