Hello Michael!

10 May 21, Michael Dukelsky wrote to Kai Richter:

 TK>>>>> How about http://download.huskyproject.org/docs/ ?

 MD>>> Is it better to remove it from wiki?

Maybe i misunderstood. Did you talked about the docs itself or the link to huskyproject?

 KR>> To provide a fast and easy access to latest documentation i'd
 KR>> like to suggest to place a prebuild .txt ascii version for each
 KR>> module to the github.

 MD> First of all I want to say that the documentation in the wiki was made
 MD> partly manually, I did not manage to make it automatically, so it
 MD> cannot be the latest version.

Date shows 2018 and that's the reason why i was looking for a more recent version. Could it become a yearly update event?

 MD> As to the latest documentation it can be made in several forms. Those
 MD> who run a UNIX-like OS may clone the GitHub repo and using a simple
 MD> command get info- and/or man-pages. From my point of view this is
 MD> better than plain ascii.

Yes, i do agree. I have to admit that i'm not on the latest version and that i'm to lazy to pull the git and do a compilation of the docs for the purpose of a check for the actual keywords when i tried to support the route configuration. I copied the text from the texi and edited it to ascii manually. Lazy as i am the idea was to have quickly accessable file for reference.

 MD> GitHub repo contains sources and it is not good to place anything
 MD> compiled from the sources to the repo including a prebuilt ascii text.

I do understand. Is it possible to use other mechanisms of github? I noticed

https://www.toolsqa.com/git/github-releases/

that github could handle releases too. But i don't know how that work. In the long term i'd like to see the project focused at one point for latest files.

Regards

Kai

--- GoldED+/LNX 1.1.4.7