I can see some benefit in distinguishing two checkouts for application
users and application developers.
What I I don't follow is why SST should be divorced into Starlink-only
development. I certainly used it for non-Starlink code, e.g. PROLAT for
making the main Appendix in SUN/232 while at JAC. If you want users to
contribute applications with documentation, then SST should be
available.
Talking of variants, GENERIC is another one to consider. I had to
modify Peter Allan's UNIX version with an extra option to generate the
filenames we expect (i.e. substitute the x suffix for the type
abbreviation, as occurred under VMS). BTW the new build system should
work from the source of generic code, i.e. expand the .gen source in to
various .f files in the build process. It's tiresome and less robust to
have to edit the same fix into several files. We're also distributing
more code than necessary (although with modern disc capacities it's not
an issue).
Malcolm
|