Folks,
On 2005 Apr 11 , at 19.37, Norman Gray wrote:
> I've also assembled the platform-specific instructions into another
> document. That's at
> <http://www.astro.gla.ac.uk/users/norman/star/sun999/>, though its URL
> will change, and it'll appear in the repository, when I get a proper
> SUN number. Should this be a SUN? Or another SSN? This is rough, as
> most of today has been spend on the manifests thing, but it's something
> to point the managers at. It would be nice to have a stable URL before
> tomorrow afternoon. Any updates happily received.
Do I allocate myself a document number? If so, do we have a mehcanism?
The file etc/info/docs_lis has a list, but it doesn't have SSN/78, for
example, and so I wonder if there are other omissions. Is this still
supposed to be the master?
All components ought to have a <documentation> element giving the
documents they include. I could knock together something which
collects all of those and make that distributed information the master,
on the grounds that anything not in the repository can be regarded as
not existing. This would involve creating componentset.xml entries for
the documents in docs/, but that should be one-off mechanical. Mmm: a
hassle.
The last SUN appears to be SUN/254, for FROG. Unless anyone shouts,
I'll designate this buildsystem document SUN/255.
Norman
--
----------------------------------------------------------------------
Norman Gray : Physics & Astronomy, Glasgow University, UK
http://www.astro.gla.ac.uk/users/norman/ : www.starlink.ac.uk
|