I imported the SVN.dumpfile as requested.
I also created a DC1 branch for the tree, which you can check out via:
svn co svn+ssh://lsstarchive.ncsa.uiuc.edu/branches/DC1 DC1
Steve
On Jun 5, 2006, at 5:27 PM, Robyn Allsman wrote:
Hi Ray,
I've just packaged up the Prototype Pipeline CVS repository into
an SVN dumpfile. It has been transferred to lsstarchive in:
[EMAIL PROTECTED]:/lsst_ibrix/rallsman/SVN.dumpfile
I'd suggest that someone more experieced with SVN do the actual
installation (svnadmin load) so that should something go wrong they
can quickly fix it.
Do you have a volunteer to handle the SVN installation for this
source?
This first installation of the prototype pipeline does NOT conform to
your suggested directory/package layout because I want to carry
forward
the CVS history into SVN. That can be done after initial
installation.
I would like the dumpfile to be installed into the SVN structure:
at the point: $SVN/trunk/applications/
The Dumpfile contains :
LSSTProto/Framework/
LSSTProto/Pipeline/WCS/
LSSTProto/Setup/
LSSTProto/README
LSSTProto/setup.py and some misc intro doc files.
I.e. directory 'LSSTProto' should be renamed to 'applications'
however
that should be done via SVN.
Also, I have not yet bundled up the sample FITS files which are
used for
validation. That takes about 169MB of space. I currently keep them in
a CVS respository. Do you want that test data to be installed under
SVN also? Otherwise, where should it be put?
Cheers, Robyn
On Fri, Jun 02, 2006 at 03:30:03AM -0500, Ray Plante wrote:
Hi DCers,
As we've discussed, we've set up a Subversion code repository on the
Precursor archive machine (lsstarchive.ncsa.uiuc.edu). Attached is
documentation detailing how to get going on it; it's also in
docushare in
our DC1 folder (Collection-472). We would very much like to have
your
feedback on both this documentation and the directory structure
we've set
up. If you have recommendations for the structure, I ask that you
try to
get those back to us by Tuesday (6/6), so that we can make changes
accordingly before we get a lot of check-ins. We can still make
changes
later than that, but nevertheless, it would be convenient to
establish a
common understanding of the structure early.
To review the structure, I recommend that you do a full check out
of the
main branch (the so-called "trunk"); see the first example in
section 2.3
of the attached documentation.
Finally, although the main driver for this repository at the
moment are
the data challenges, we intended this to be open to all new DM code.
However, I would like to let the DC folks shake it out first (say,
over
the next week) before we add too many more users.
thanks,
Ray
--
Roberta (Robyn) Allsman
Large Synoptic Survey Telescope phone: 520-322-8741
Data Management FAX: 520-881-2627
4703 E. Camp Lowell Dr Suite 253 email: [EMAIL PROTECTED]
Tucson, AZ 85712 USA
_______________________________________________
LSST-data mailing list
[email protected]
http://www.lsstmail.org/mailman/listinfo/lsst-data
_______________________________________________
LSST-data mailing list
[email protected]
http://www.lsstmail.org/mailman/listinfo/lsst-data
