[NLPL Task Force (A)] NLPL parsning

Stephan Oepen oe at ifi.uio.no
Mon Dec 16 23:03:13 UTC 2019


hi ali and joerg,

> Thanks for your help with access to the module directory. I too could copy our module files.

Saga uses a newer version of the software modules environment, where
module definitions should be written in Lua now (rather than in Tcl);
this is uniform between norway and finland, so i would recommend you
rewrite the UUParser module file in Lua.  please see some of the other
existing modules for inspiration.

> I (username: abasirat) still need writing access to '/cluster/shared/nlpl/software/sources' to install 'uuparser' in the directory.

i see that joerg has created this directory, but our current
installation guidelines actually prescribe that both build scripts and
sources should (optionally) go into .../software/build/.

ali, so please just use .../software/build/uuparser/ (which you should
be able to create).

joerg, could you please (on Saga):

cd /cluster/shared/nlpl/software
mv build_scripts build/common
mv sources/* build
rmdir sources

also, for the nightly backups to be happy, it needs to be the case
that i can read all files: could you make the 'common' installation
script run something like the following upon completion:

chgrp -R nlpl ...
chmod -R g+rX ...

finally, i think .../software/modules/nlpl-common/ really should be
called just 'common' (while the module definition should be
'nlpl-common').  apologies for all the nit-picking, but as we rebuild
everything these days, i would be in favor of increasing consistency
(even) further.

best wishes, oe



More information about the infrastructure mailing list