On Fri, 30 Jul 2004, Norman Gray wrote:
> Tim,
>
> On 2004 Jul 30 , at 03.18, Tim Jenness wrote:
>
> > It occurs to me now that I've finally had a chance to look at IFD
> > (JCMTDR now uses it!), and now that OSX by default ships with a bash
> > shell, that it is entirely feasible for ifd2star to produce
> > sh format as well as csh format. The code seems to be fairly
> > straightforward, and it naively looks like all that is required is to
> > clone each line containing pkg_csh with the equivalent pkg_sh
> > invocation.
> >
> > I see that Norman actually has an esp.sh in CVS...
>
> I never could abide csh.
>
> I would imagine, in any case, that this is better done with shell
> aliases or functions, working from the manifests or some processed
> version of them. To show how easy this is, here's a bit of sh code
> I've been using, which generates sh setups of some packages, including
> getting the version number from the .csh file:
better than the IFD system for apps that currently have ifd files???
Surely you jest. Or are you saying it should be easier to generate this
stuff from the TASKS list for non IFD-ified apps
[but that doesn't help non-ADAM scripts]?
Are you saying that IFD Should not longer generate .icl or .csh files?
--
Tim Jenness
JAC software
http://www.jach.hawaii.edu/~timj
|