I agree with P.O. regarding building documents. The most I’d expect is a build (plain text) document that would list dependencies, including minimum version, as well as their home.
Personally, I’ve always built oorexx from source, but I’ve never found it necessary to build the docs. Bruce Sent by Magic! > On Dec 21, 2022, at 8:54 AM, P.O. Jonsson <oor...@jonases.se> wrote: > > Dear Gil, > > In my experience every URL is invalid the next time you try to use it :-) so > my approach is another one. For macOS and Linux I included zipped folders > with a set of tools that DID work when I zipped them, as well as a list of > requirements that the user must take care of him/herself. In that way it > should be possible to get going, also if some of the tools are out of date. I > cannot imagine that too many people besides the two of us actually build the > documentation for ooRexx voluntarily :-) > > Hälsningar/Regards/Grüsse, > P.O. Jonsson > oor...@jonases.se > > > > >> Am 21.12.2022 um 17:37 schrieb Gilbert Barmwater <gi...@bellsouth.net>: >> >> When I first wrote setup.rex the goal was to make it easy for the new >> (Windows) user to get all the pieces needed to build the ooRexx >> documentation. Most of those pieces were pretty straight forward as they >> were fairly static so coding web addresses and file names was not a problem. >> FOP however was a different story. There is active work ongoing for this >> project so the version, and hence the file name, changes from time to time. >> This was reported first by Jean_Louis and it resulted in an update to >> dynamically determine the most recent version from the Apache web site and >> download it as opposed to trying to download an older version which might >> have been archived and hence not where the current version was located. Now >> it appears that the mirror sites which is where one must go to download the >> files also changes from time to time. <sigh> I will work on automating the >> determination of the mirror site and update the script once I do. In the >> meantime, around line 191 is the URL of the mirror site which has apparently >> gone away. If you replace it with >> "https://dlcdn.apache.org/xmlgraphics/fop/binaries/";, the now suggested >> mirror for downloads, it should run successfully. NB. I have NOT actually >> confirmed that at this time. >> >> Gil >> >> On 12/20/2022 9:14 AM, Rony G. Flatscher wrote: >>> Just used "tools\bldoc_orx\setup.rex" and get the following error: >>> >>> Downloading fop-2.8-bin.zip >>> Start-BitsTransfer : HTTP-Status 404: Die angeforderte URL ist auf diesem >>> Server nicht vorhanden. >>> At line:1 char:1 >>> + Start-BitsTransfer https://mirror.nodesdirect.com/apache/xmlgraphics/ ... >>> + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> + CategoryInfo : InvalidOperation: (:) [Start-BitsTransfer], >>> Exception >>> + FullyQualifiedErrorId : >>> StartBitsTransferCOMException,Microsoft.BackgroundIntelligentTransfer.Management.NewBitsTransferCommand >>> >>> Error retrieving fop-2.8-bin.zip; RC was 1. >>> >>> It is at: <https://archive.apache.org/dist/xmlgraphics/fop/binaries/>. >>> >>> The script uses >>> "https://mirror.nodesdirect.com/apache/xmlgraphics/fop/binaries/"; which >>> returns a 404. >>> >>> ---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 > > _______________________________________________ > 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
