I noticed you guys built in an experimental feature to package the software
with fpm.
Very interesting, so I started to play with it.
In my test the packaging fails, because the last value added to the fpm
command is the easyblock.module_generator.filename
$ eb -f --experimental --package h/htop/htop-1.0.3.eb
Somewhere in the code it performs this command:
$ fpm --workdir /tmp/eb-wPSfdd/eb-pkgs-MYbJ1r --name htop-1.0.3 --provides
htop-1.0.3 -t rpm -s dir --version eb-2.2.0 --iteration 1 --depends
'ncurses-5.9' /path/to/install/htop/1.0.3 /tmp/eb-wPSfdd/tmpLp_97M/all/htop/
1.0.3
tools/package/utilities.py:
cmdlist = [
PKG_TOOL_FPM,
'--workdir', workdir,
'--name', pkgname,
'--provides', pkgname,
'-t', pkgtype, # target
'-s', 'dir', # source
'--version', pkgver,
'--iteration', pkgrel,
depstring,
easyblock.installdir,
easyblock.module_generator.filename,
]
After creating the "real" module, make_devel_module is called and it
overwrites the module filename. Thus gives the path seen above.
The moment fpm gets invoked the path doesn't exist anymore (it uses the
temporary build path).
Have I done something wrong with my install of EB 2.2.0?
