On Sat, 29 May 2004, Norman Gray wrote:
> Probably at the programmers' meeting:
Okay. Can me make that a morning session so that I can chip in from
Hawaii?
>
> - I'll give a summary of where we're at with this, for the benefit of
> those who haven't been experimenting already, and/or who aren't coming
> to the CVS-week. I'll also make sure I can again produce paper
> documentation by then.
>
> - The tagging and releasing procedures that I mentioned on the wiki
> page, and that Mark and I discussed in outline on the list a couple of
> weeks ago. This _has_ to have Steve's input, I think.
>
> - Installation locations: In the stardev thread `[CVS] AST and
> general starconf issues', starting 4 April, we talked over whether
> Starlink applications and libraries should be installed in the
> `standard' places -- all libraries in lib/, all platform-neutral files
> like help files in share/, and so on. We didn't come to any
> conclusions. Again, this needs Steve's input.
>
Pre-empting the discussion, I don't think it's an issue since most things
can migrate from the current installation locations to a new
"standardised" location without affecting other things. This is easy once
everything works in CVS. [although we did agree that we should not be
installing shared libraries into share]
> Anything else? Is that a reasonable division?
>
The install target needs to install versioning information somewhere so
that the starversion command will continue to work. Currently starversion
mainly looks in the datestamp files but there is no equivalent at the
moment.
--
Tim Jenness
JAC software
http://www.jach.hawaii.edu/~timj
|