when building ooRexx on *nix the rexx.img file is just put into /opt/oorexx/usr/bin. The file is loaded via the path, and this directory is part of the path (.). When building a package for a specific architecture there may be the requirement that the rexx.img is moved outside the bin directory.
For example, Debian only allows executable files (ELF or scripts) to be located in /usr/bin. As I'm currently trying to build an ordinary Debian package I'm facing this problem. With the current sources it is not possible to move the rexx.img anywhere else.
To overcome this limitation I would like to have an enhanced rexx executable offering parameters to load and save image files.
By doing this it would also be possible to create other images.
According to the Debian file system hierarchy the rexx.img needs to go to /usr/lib/ooRexx/rexx.img (architecture depended private file).