New beta

[Werner Koch]

On Sun, 21 Sep 2014 03:47, mac3iii at gmail.com said:

> for me I cannot then get it to perform its duty.  I execute the
> suggested command
> LD_LIBRARY_PATH=$(pwd)/PLAY/inst/lib
> typed exactly as written above, and then nothing happens.  gpg2
> continues to execute as the previously installed version.  Any ideas?

Weel the above is not a command but the way to set variables in the
shell.  Programs won't pick these variabales up unless you do either

  NAME=VALUE PROGRAM

or for setting it for the entire session you need to mark the variable:

  NAME=VALUE
  export NAME

after that all programs can access this variable.  Now to run the actual
binary you have to type the name of the program:

  PLAY/inst/bin/gpg2 

assuming you are in the top build directory or you add it to your PATH

  PATH="$(pwd)/PLAY/inst/bin:$PATH"

(An "export" command for PATH has already been done by tye shell)

> admit, I am relatively new to Linux but can somebody give me a hint as
> to what is meant by ../?  A simple command to create the required

The parent directory.  I suggest that you read up a bit on Unix shell
use because all build instructions are written under the assumption that
is is known.

Yes, I know that this is the gnupg-isers mailing liste and we should not
assume that all subscribers are Unix gurus.  However, in the past that
seems to have been the case. 


Salam-Shalom,

   Werner


-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.