On Fri, 15 Jun 2007, Tim Jenness wrote:
> Subversion import has completed
I've just completed a build from subversion and it seemed to work okay
(although there was a problem with the skycat import - it seemed to be
confused about which files were current). Keep an eye out for corrupt
binaries (I caught most - cgs4dr had some because I added that to obsolete
at the last moment) - images can be seen on the "viewvc" web page.
Things that need to change:
- Can someone change dev.starlink.ac.uk to provide new anonymous
checkout instructions (noting that Java is still in CVS)?
- The bootstrap script complains if CVS directory is missing (it checks
to make sure that relevant files are in CVS. bootstrap needs to be
changed to use subversion (I think that 'svn status -v filename' will
be good enough because that does not require remote access to the
repository)
- the nightly builds need to switch to using svn checkout rather than
cvs
- I'll try to get the new summarize-commits script up and running soon.
- I'll ask Brad to move the starlink JAC web pages from their current
location to http://starlink.jach.hawaii.edu
- one of the points of this is to provide a single revision number for
the DR code. This requires that systems can work out the global
revision. I think this means that for every 'make install'
the output of svnversion (preferably from the build root directory)
installs a file in $STARLINK/manifests (?) called 'starlink.version' (?)
Does this sound reasonable?
> svn checkout svn+ssh://ssh.jach.hawaii.edu/jac_sw/svnroot/starlink/trunk
> star
>
> or (if you don't have JAC ssh access or prefer webdav)
>
> svn checkout https://starlink.jach.hawaii.edu/svn/trunk star
>
Note that this will work without requiring password be entered except for
the first commit. This may be preferable to ssh access unless you have
keys set up with the JAC.
--
Tim Jenness
JAC software
http://www.jach.hawaii.edu/~timj
|