Is it possible in the VCL repository to have a reference to a remote Dojo Subversion repository? That way VCL could be using the head of a branch of Dojo without using trunk (with all the support issues that entails). If you did an svn checkout you'd get Dojo, but the VCL team wouldn't have to keep parallel with the Dojo repository.
Keeping up with the Dojo API is something that has to be done by developers to make sure the web interface always functions, but keeping up with it at the Subversion level within the VCL repo doesn't seem like a good idea. -- Tony Miller Technology Consultant, ITCS, East Carolina University Austin 106N /\ 252-737-1515 /\ mill...@ecu.edu /\ http://blog.ecu.edu/techtips -----Original Message----- From: Josh Thompson [mailto:josh_thomp...@ncsu.edu] Sent: Wednesday, May 30, 2012 3:04 PM To: vcl-dev@incubator.apache.org Subject: copy of dojo in the repo? -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Recently, the idea of maintaining a copy of the Dojo Toolkit in the subversion repository has been brought up. I've avoided maintaining dojo in subversion both to keep the repo a little cleaner and to avoid the problem of ending up with an old copy in there that never gets updated. However, the decision to have it in the repo is really up to the community - not just up to me. Would others prefer for it to be there? Not having it there requires the extra step of downloading it from another location and installing it if you want to try to install VCL from subversion. This only takes a few minutes, but it is still a few extra steps. Additionally, installing VCL from subversion may or may not work, depending on the state of development. We don't typically check in things that are unfinished, causing trunk to be broken, but there's always the possibility of that happening. Josh - -- - ------------------------------- Josh Thompson VCL Developer North Carolina State University my GPG/PGP key can be found at pgp.mit.edu All electronic mail messages in connection with State business which are sent to or received by this account are subject to the NC Public Records Law and may be disclosed to third parties. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iEYEARECAAYFAk/Gbx0ACgkQV/LQcNdtPQPY/gCfUmyf0Lpi/w0DRtj9xBO5DgSj 3nsAnjMWSDkIx4QPIcqljMviAJNbef41 =t5rH -----END PGP SIGNATURE-----
