Re: [PATCH] sln: Install as a hard link to ldconfig

[Joseph Myers <joseph at codesourcery dot com>]

On Tue, 2 Aug 2016, Florian Weimer wrote:

> Can you provide an exact quote?  I don't see it.  coreutils supports this, and
> bash pretty much requires looking at argv[0].

There are at least two relevant quotes in standards.texi:

  @node User Interfaces
  @section Standards for Interfaces Generally

  @cindex program name and its behavior
  @cindex behavior, dependent on program's name
  Please don't make the behavior of a utility depend on the name used
  to invoke it.  It is useful sometimes to make a link to a utility
  with a different name, and that should not change what it does.

  Instead, use a run time option or a compilation switch or both to
  select among the alternate behaviors.  You can also build two versions
  of the program, with different names and different default behaviors.

and, for --version:

  The program's name should be a constant string; @emph{don't} compute it
  from @code{argv[0]}.  The idea is to state the standard or canonical
  name for the program, not its file name.  There are other ways to find
  out the precise file name where a command is found in @code{PATH}.

-- 
Joseph S. Myers
joseph@codesourcery.com