Greetings,
Can I just check: when applications are installed in package-specific
directories, is it only INSTALL_BIN and INSTALL_HELP which are given
package-specific paths? That seems to be the case for sst, atools,
ccdpack and kappa (for example), but is that quite general? It just
seems slightly arbitrary, though I can see that it makes sense
inasmuch as there wouldn't be namespace clashes for libraries in the
same way there would be for tasks.
Partly I'm saying this because it's a mild pain to configure this
automatically, as well as being probably slightly hacky. It occurred to
me that a reasonably straightforward alternative would be to install
applications in the normal bin directory with a package-specific
prefix, and then add a package-specific directory which linked to it:
thus installing
/star/bin/kappa-maths
/star/bin/kappa/maths -> ../kappa-maths
and the same for the .ifc files. Would this obviously break? Would the
.ifc files stop working if the task name within them were different from
the argv[0] of the binary which invokes them (no, from what I understand
of them, but that's not much)?
This route quite possibly has other problems with it, and might end up
hackier than doing it the original way. But if there are showstopping
problems that I haven't thought of, then I can stop worrying and learn
to love the hack....
See you,
Norman
--
---------------------------------------------------------------------------
Norman Gray http://www.astro.gla.ac.uk/users/norman/
Physics and Astronomy, University of Glasgow, UK [log in to unmask]
|