The reason for putting the package, at least the non-binary files, on
SVN is to make them officially part of the ooRexx project. That way,
anyone can modify them when the need arises (at least anyone with
committer status). 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. We certainly should create a version
of the package that runs on *ix so anyone not on Windows can also build
the documentation. And I am sure there are others as well.
I am happy to also put the "complete" package up as well, presumably in
the Files section where the Publican-related tools are stored, but I
will need some direction on how to do so.
Gil
On 4/16/2020 1:28 PM, P.O. Jonsson wrote:
I agree with Jeremy, I spent a LOT of time trying to resurrect
Publican and would not have succeeded unless Erich had saved some of
the necessary items on Sourceforge. I am in favor of saving a complete
standalone package.
I don´t see a point with using SVN to get the tools. If there is a
„Tools“ repository that one can use http to get to this is easier for
most user?
Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se <mailto:oor...@jonases.se>
Am 16.04.2020 um 18:58 schrieb Jeremy Nicoll
<jn.ml.sfrg...@letterboxes.org <mailto:jn.ml.sfrg...@letterboxes.org>>:
On Thu, 16 Apr 2020, at 15:08, Gil Barmwater wrote:
The problem that arises is
that the complete package contains binary files which are not normally
kept in SVN. So I can either upload the entire package anyway or just
upload the parts that are not obtained from the Internet and write
detailed instructions on what and how to obtain the other portions. The
first has the advantage that the package is immediately usable once it
is checked out while the second is much "cleaner" but requires the user
to do additional "installation" work before it can be used.
If there's not at least a reference copy of the binaries then in a
few years
time, when the external tools change, it might impossible for other
people
to repeat the current process.
If on the other hand the current binaries are also stored, they
should be
runnable in future if necessary (even if that has to be done in a virtual
machine running some ancient OS like Windows 10).
--
Jeremy Nicoll - my opinions are my own.
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
<mailto:Oorexx-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
--
Gil Barmwater
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
