cool. Ter On Aug 15, 2008, at 4:31 PM, Johannes Luber wrote: > Terence Parr schrieb: >> On Aug 15, 2008, at 4:05 PM, Johannes Luber wrote: >>> Terence Parr schrieb: >>>> Hi Ben, >>>> Great idea. At the moment I see: >>>> ~/antlr/code/antlr/main/runtime $ ls */dist >>>> C/dist: >>>> libantlr3c-3.0.1.tar.gz libantlr3c-3.1.tar.gz >>>> libantlr3c-3.1.1b1.tar.gz >>>> Python/dist: >>>> antlr_python_runtime-3.1-py2.4.egg >>>> antlr_python_runtime-3.1.tar.gz >>>> antlr_python_runtime-3.1-py2.5.egg >>>> antlr_python_runtime-3.1.zip >>>> Should just add an scp for any target that has that in their >>>> runtime dir? >>>> Johannes, you could add that right too? >>>> Ter >>> >>> You mean, that every time I update the runtime, that the >>> assemblies, etc. are added into the repo? How do you version the >>> runtime-dists then, once you create the zip? Or am I supposed to >>> create the zip myself and to add it into the repo? Not sure if I >>> like the dists in the repo... Can one safely remove older zips >>> without prompting scp to delete them from the target directory? >> yep. delete from depot. scp will only add not delete unless i >> rsync. Just put whatever runtime distribution stuff should go to >> download/CSharp into that dist dir and I'll copy it over. Make >> sure it's named something reasonable. >> Ter > Will start with this for the 3.1.1 release. > > Johannes
_______________________________________________ antlr-dev mailing list [email protected] http://www.antlr.org:8080/mailman/listinfo/antlr-dev
