Hi Loris, Installing hidden modules after the fact won't help you here unless you rebuild your entire stack of modules (since all modules will need to be rewritten to include the now-hidden dependencies). We use a config option to define a default set of hidden modules:
EASYBUILD_HIDE_DEPS=ANTLR,APR,APR-util,AT-SPI2-ATK,AT-SPI2-core,ATK,Autoconf,Automake,adwaita-icon-theme,ant,assimp,Bison,babl,binutils,byacc,bzip2,CUSP,Coreutils,cairo,cling,configurable-http-proxy,DB,DBus,DocBook-XML,Dyninst,dbus-glib,damageproto,ETSF_IO,Exiv2,eudev,expat,FFmpeg,FLTK,FTGL,FoX,fixesproto,fontsproto,fontconfig,freeglut,freetype,GCCcore,GDAL,GEGL,GL2PS,GLEW,GLM,GLib,GLPK,GPC,GObject-Introspection,GTI,GTK+,GTS,Gdk-Pixbuf,Ghostscript,GraphicsMagick,GtkSourceView,g2clib,g2lib,gc,gexiv2,gflags,glog,glproto,googletest,gperf,guile,grib_api,gsettings-desktop-schemas,gettext,gzip,HarfBuzz,icc,ifort,inputproto,intltool,itstool,JUnit,JSON-C,JSON-GLib,JasPer,jhbuild,kbproto,LMDB,LZO,LevelDB,LibTIFF,LibUUID,Libint,LittleCMS,libGLU,libICE,libSM,libX11,libXau,libXaw,libXcursor,libXdamage,libXdmcp,libXext,libXfixes,libXfont,libXft,libXi,libXinerama,libXmu,libXp,libXpm,libXrandr,libXrender,libXt,libXtst,libcerf,libcroco,libctl,libdap,libdrm,libdwarf,libelf,libepoxy,libevent,libffi,libfontenc,libgd,libgeotiff,libglade,libidn,libjpeg-turbo,libmatheval,libmypaint,libpng,libpciaccess,libpthread-stubs,libreadline,librsvg,libsndfile,libspatialindex,libtool,libunistring,libunwind,libyaml,libxcb,libxkbcommon,libxml2,libxslt,libyuv,M4,MATIO,Mesa,makedepend,motif,msgpack-c,NASM,NLopt,ncurses,nettle,nodejs,nvenc_sdk,nvidia,OPARI2,OTF2,PCRE,PDT,PROJ,Pango,Pmw,PnMPI,PyCairo,PyGObject,Python-Xpra,patchelf,pixman,pkg-config,pkgconfig,popt,printproto,protobuf,pscom,pybind11,Qhull,Qt,Qt5,qrupdate,randrproto,recordproto,renderproto,S-Lang,SCons,SIP,SQLite,SWIG,Serf,Szip,scrollkeeper,snappy,Tk,texinfo,UDUNITS,util-linux,vpx,wxPropertyGrid,wxWidgets,XML-Parser,XZ,XKeyboardConfig,x264,x265,xbitmaps,xcb-proto,xcb-util,xcb-util-image,xcb-util-keysyms,xcb-util-renderutil,xcb-util-wm,xextproto,xineramaproto,xorg-macros,xprop,xproto,xtrans,Yasm,zlib You can also tell Lmod to hide certain modules (which is something you can do after the fact) via a hook (but I haven't done this): https://lmod.readthedocs.io/en/latest/170_hooks.html?highlight=hidden Alan On Fri, 23 Nov 2018 at 10:17, Loris Bennett <[email protected]<mailto:[email protected]>> wrote: Hi Sam, Thanks for the info about rebuilding the module files. Regarding the visibility of modules, I just want to exclude some from the results of 'module av'. I assume 'module list' will still show all the modules which are loaded, hidden or not. That doesn't bother me, since, as far as I know, very few of our users look at the output of 'module list' anyway. Cheers, Loris Sam Moors <[email protected]<mailto:[email protected]>> writes: > Hi Loris, > > You can instruct EB to only rebuild the modules with the '--module-only' > option. > I don't know about your second question though. > > That said, are you sure you want to hide the dependencies? > I think it is useful for the users to know which deps are loaded, so > they can avoid conflicts with other modules, even if it may look > daunting to see 50+ modules loaded in some cases. > > Cheers, > Sam > > On Fri, Nov 23, 2018 at 8:25 AM Loris Bennett > <[email protected]<mailto:[email protected]>> wrote: > > Hi, > > Now that I have installed a couple of packages with easybuild I have a > surprising number of modules and realise that I should have been using > --hide-deps. I have two questions about this: > > 1. Is there any way to retrospectively hide modules, other than tweaking > the module files by hand, say, rebuilding the modules? > 2. Can a set of modules be defined which will be hidden by default? > > Cheers, > > Loris > > -- > Dr. Loris Bennett (Mr.) > ZEDAT, Freie Universität Berlin Email > [email protected]<mailto:[email protected]> > > -- Dr. Loris Bennett (Mr.) ZEDAT, Freie Universität Berlin Email [email protected]<mailto:[email protected]> -- Dr. Alan O'Cais E-CAM Software Manager Juelich Supercomputing Centre Forschungszentrum Juelich GmbH 52425 Juelich, Germany Phone: +49 2461 61 5213 Fax: +49 2461 61 6656 E-mail: [email protected]<mailto:[email protected]> WWW: http://www.fz-juelich.de/ias/jsc/EN ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr. Sebastian M. Schmidt ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------
