We can always locate them using dpkg if we are unsure of their names, so a
prefix or other small adjustment should be fairly innocuous.
--
Sent from my mobile device.
Daniel Kahn Gillmor <d...@fifthhorseman.net> wrote:
>On 03/22/2013 01:51 AM, Mike Hommey wrote:
>
>> I'm not particularly happy with binaries with pretty generic names
>> ("addbuiltin" is a good example of such) ending up in /usr/bin...
>> But you can try to convince me otherwise. Or move them in some other
>> directory.
>
>hm, i think the following new binaries should be unobjectionable in
>/usr/bin :
>
>p7content
>p7env
>p7sign
>p7verify
>symkeyutil
>ocspclnt
>chktest
>derdump
>rsaperf
>vfychain
>vfyserv
>
>
>These two TLS client utilities and two TLS server utilities have
>somewhat generic names, but i think are useful enough to ship in
>/usr/bin despite the genericness (they can be used along with
>gnutls-cli
>and gnutls-serv and "openssl s_client" and "openssl s_server" to do
>interop testing for new TLS clients and servers, for example):
>
>strsclient
>tstclnt
>httpserv
>selfserv
>
>The following three are the most dubious in terms of names:
>
>addbuiltin
>pp
>dbtest
>
>i'd be fine shipping the last category and optionally the client/server
>utilities with an nss- prefix if you think that would be more
>acceptable. I'd rather not move them entirely out of the $PATH if
>possible. and i'd prefer to not rename existing tools that we have
>already been shipping in libnss3-tools, of course.
>
>Would you like me to prepare an alternate patch that does that renaming
>on one or both groups?
>
> --dkg
