Martin Gasbichler <gasbichl@informatik.uni-tuebingen.de> writes:
[...]
> I'm also thinking about installing the program scsh-config that
> prints some installation related informations to stdout. scsh-config
> is currently simply generated in the top-level of the build
> directory but not installed in $prefix/bin. At least scx, our
> library for accessing Xlib, could make use of scsh-config but I'm
> not sure if it is generally useful at the moment. Opinions?
I think it's generally useful to have that, yes. I wonder, however, if
this could not be simply integrated in scsh itself, via some new
options (say "scsh -config ..."). I tend to prefer that solution
simply because it puts one less executable in the path, but that's a
detail.
Now that I think about it, why not do the following:
- make all configuration parameters accessible in scsh through
variables or functions,
- provide a new option for scsh, say -p, which evaluates an
expression, print its result and then exit (i.e. does what -c
does, but additionaly print the result of the evaluation).
That way, instead of writing
scsh-config --libs
one could write
scsh -p scsh-config-libs
Michel.
|