[NLPL Task Force (A)] clarification of NLPL installation guide

[Stephan Oepen]

dear all,

thanks for a productive meeting today.  per our discussion, i just
updated the installation guide to require the ‘nlpl-’ prefix on module
definitions and started writing down some general principles for
long-term sanity (e.g. ‘one fact, one place’):

   http://wiki.nlpl.eu/index.php/Infrastructure/installation/guide

i also added a column to record the maintainer (and contact person) to
the software catalogue:

  http://wiki.nlpl.eu/index.php/Infrastructure/software/catalogue

i would like to point the team towards the guide and catalogue
sometime tomorrow afternoon.  anyone with a few minutes to spare
tomorrow before noon, please take a look and send me corrections or
comments!

joerg, many thanks for the various software and data installations you
have put onto both systems!  since you were the one to talk me into
stricter compliance with the guide developed by thomas originally, i
feel like returning that favour now :-).

+ in my view, we should religiously avoid soft links; there should be
one unique path that refers to each resource.  for example, it should
either be ‘opus’ or ‘OPUS’, but not both.  since the guide requires
all lower-case, how difficult would it be to make it
‘$NLPL/data/opus/’ still?

+ i hope you will welcome us mandating the ‘nlpl-’ prefix on module
names, even though that late decision will now cause you a little
extra work in renaming files below ‘modulefiles/’; but unless i am
overlooking something, that is actually all that needs to be done to
change the module name, right?

+ i think there should be a direct correspondence between the module
name and its location: for example, the ‘nlpl-opus’ module should have
its associated binaries and data below $NLPL/software/opus/ (not
‘opus-tools’, unless the module were called ‘nlpl-opus-tools’).

+ it appears there is a ‘stray’ installation of perl in the top-level
‘software/’ directory, i.e. ‘bin/’, ‘lib64/’, ‘man/’, and ‘share/’.
my initial reaction is that these directories should not be there.  i
know little about perl, but i am guessing we might need additional
modules besides what comes with the system-wide perl module?  if so,
my gut feeling still would be that these should somehow be packaged as
a module ‘nlpl-perl’, parallel to everything else.  would that be
possible?  a bit like a virtual environment in python?

+ i see there are personal dirctories ‘.subversion’, ‘.emacs.d’,
‘.gitconfig’, etc. inside $NLPL/software.  i am guessing somehow that
directory served as your $HOME at some point, but in my view those
user-specific directories should not be there.

—so much with the nit-picking tonight :-).  sorry to mostly targeting
you, joerg!  but i hope the perfectionist in you may nevertheless kind
of appreciate the feedback?

all best, oe