I would vote that we not include code for which we are not responsible.
However, it may be good to keep tarballs of the versions of each
external package that we depend upon just in case something unexpected
On Wed, May 30, 2012 at 3:03 PM, Josh Thompson <josh_thomp...@ncsu.edu> wrote:
> -----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 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)
> -----END PGP SIGNATURE-----