I've just pushed the change from SC18->SC19. I'll leave the cookbook where
it is for now, but it can easily be moved later if desired. In principle I
agree with you -- while being very SMURF-centric, it also refers to Kappa
and Gaia a fair bit.
Ed
>> Sure, I can increment to SC19. I guess this X-ray doc should be listed in
>> star/docs/docs_lis as well.
>
> Indeed. I've updated etc/info/docs_lis but not committed it yet.
>
>> Being a relative newcomer to starlink development, I have no preference as
>> to where the SMURF documentation gets stored. Currently we have SC18/19,
>> SUN257 and SUN259. Perhaps Tim has a strong opinion here.
>
> The SUN or SSN relatively exclusively to a package goes with the package.
> Cookbooks were intended to be pan-package, hence should be in their own
> domain, not tied to one package. I suppose if you're only documenting how to
> use one package the Cookbook could go with the package itself. Then you
> might argue that information could go in the package SUN. As a programmer
> it's easier to find them if they're together. Of course, in the installed
> /star tree they are. It's not that inmportant, it just goes against my
> sensibilities.
>
> Malcolm
>
|