Re: [tei-council] Test GLs repo on GitHub

On Aug 2, 2015, at 12:39 , Martin Holmes wrote:

This brings up something I don't adequately understand:

Is it possible to have a single repo on GitHub, and simultaneously access it through git and svn? That seems very unlikely.

I think the svn interface has some limitations, but yes, you should be able to do exactly that.

Assuming that's not the case -- or assuming it's inadvisable because it would result in all sorts of confusion -- then we could consider first moving everything to GitHub but staying with svn, and then later transitioning to git. That would be much easier initially, and it would also enable us to move rather quickly in answer to the perceived fragility of SourceForge without having to immediately undertake the more complex transition to git.

There are lots of script calls that depend on svn (getting the svn revision number, for instance).

Things like that and the uploads would indeed need to change. Getting the rev number is straightforward, but we would need to come up with a new process for uploading releases, as you note below.

But there are also commands which upload packages to SourceForge directly, with dependence on SSH keys and the like -- this from tei-install.sh is an example:

upload() { echo upload ${pname}-${version}.zip to Sourceforge ${SFNAME} as user ${SFUSER} ${ECHO} rsync -e ssh ${pname}-${version}.zip ${SFUSER},tei@frs.sourceforge.net mailto:tei@frs.sourceforge.net:/home/frs/project/t/te/tei/${SFNAME}/${pname}-${version}.zip }

My all-too-cursory reading of the GitHub docs suggests that the equivalent would have to be achieved as part of a release using curl against the GitHub API; I don't think you can simply rsync a file up to GitHub and have it appear as a release. So while switching to GH with svn rather than git would definitely simplify a lot of things, doing an actual release would not be simply a matter of changing URLs.