Having given this some more thought, I now propose to 1) place the
"non-external" portions of the package in SVN as I originally proposed
and 2) place a copy of each of the zip files, the files that are
actually downloaded from the Internet by the Setup program, in an
appropriate place in the Files section of the SourceForge ooRexx site.
This addresses the concern of having a "backup" copy of the external
tools while not having two copies of the other files that would require
synchronization.
Gil
On 4/16/2020 3:58 PM, Jeremy Nicoll wrote:
On Thu, 16 Apr 2020, at 18:59, Gil Barmwater wrote:
I do not believe by any means that this is the
"last" version of these tools. For example, we should look at moving to
DocBook 5 and that will surely involve changes. We might want to
explore using a different tool to do the transform, one that might
support syntax highlighting of our code examples.
I'm not against that in any way. What I am suggesting is that whatever
is the toolset du jour, there should be a complete copy of that stored
by this project, not dependent on external repositories.
--
Gil Barmwater
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
