Just a thought but didn't we start with our code in CVS rather than SVN?
Perhaps that is why 3.0.0 and 3.0.1 are missing.
Gil
On 12/31/2022 12:14 PM, Rony G. Flatscher wrote:
On 30.12.2022 13:21, ooRexx wrote:
- Sourceforge could bring most of the documentation back, 3.0.0 and
3.0.1 I extracted from the Windows installers (that still work, 17
years later!). I have set the date of the documentation same as the
artifact folders.
+1
Note: 3.0.0 and 3.0.1 are missing from {main|docs|test}/releases
altogether.
- all platforms build without problems, including Mark Hessling's M1
Mac running Ventura (macOS 13)
+1
- (almost) all test passes, some things todo for 5.1.0 (more about
that next year)
I found something interesting in the 4.1.3 documentation:
ooRexx-4.1.3-all.zip
ooRexx-4.1.3-html.zip
ooRexx-4.1.3-pdf.zip
Would it make sense to make the same for 5.0.0 (at least the -all)? I
find it really annoying with the delayed downloading on sourceforge.
Yes, "-all" would be of help.
As Enrico pointed out the revision number should not show for a
released version. I do not know how to fix this (5.0.1?) but we also
have the revision number in the artifact (installer) filenames
(controlled by CMake) -> we should look at how to change this for a
release version and document that for the next time.
We can manually remove this from the filenames for 5.0.0 but since
rexx -v will still show it I don“t think it is necessary?
Yes, would leave the filenames with the revision as long as "rexx -v"
shows a revision.
This can probably be done with changes to CMakeLists.txt. Not sure
what the best approach would be (e.g. a flag "NOREV=1" to inhibit
revision information in the produced interpreter and the produced file
names). Enrico, as a CMake expert what do you think would be a
sensible approach/solution?
---
Once we have a solution we could try to create refreshed installation
and portable packages from main/releases/5.0.0 with
docs/releases/5.0.0 if that is manageable for P.O. which probably
means to adjust the Jenkins scripts first. Maybe Erich can be of help
here?
---
Anyway, have all a great Silvester (if still applicable) and a great
New Year 2023 in any case!
---rony
_______________________________________________
Oorexx-devel mailing list
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