Dear Rony,
I can not judge if this affects the “official” building & uploading of
documentation. Currently we keep a simple log of what revision every book has.
If I understand it correctly the revision of a single book (the top level
folder) gets incremented as soon as ANY change is made to a document within
that folder. We use svn log <book> to find that out.
What you are proposing - does that require a change in the documentation
building script?
Hälsningar/Regards/Grüsse,
ooRexx
oor...@jonases.se
> On 22. Dec 2022, at 14:27, Rony G. Flatscher <rony.flatsc...@wu.ac.at> wrote:
>
> Sleeping over this revision problem in the context of the documentation there
> is another problem with them in the case we must update the copyright notes
> in the files: each file that gets changed and committed will get a new
> revision which does not reflect the revision of the last change of the
> documentation.
>
> Here an additional approach to solve this: if there is a file
> ${book}/revision_info.txt (this file needs to be created by the script with
> the revision information as the only content and can then be edited manually
> from then on) then use its content for the revision information and do not
> inspect the revisions of the individual documentation files. If that
> ${book}/revision_info.txt is missing, then go ahead and try to figure out the
> revision information with the current logic (and create
> ${book}/revision_info.txt with the revision information).
>
> If one uses the current logic first (in addition will ignore the revision of
> "Authors_Group.xml") - before updating the copyright information - and then
> creates those ${book}/revision_info.txt files the revision information
> remains the same until sometimes in the future the file gets updated (to run
> the fallback logic in the future one would need to rename or delete
> ${book}/revision_info.txt, such that the fallback logic takes effect).
>
> Enclosed the updated script (needs to go into tools).
>
> ---
>
> If this is o.k. for everyone I would use it to set EDITION to "2022.12.24"
> (to distinguish it from the current) and have the revision information
> created and appended to it, including creating revision_info.txt which I
> would add to be committed as well (rerunning is almost instantaneous with it).
>
> ---rony
>
> ... cut
> ...<updateEntityValues.rex>_______________________________________________
> 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
