Hello Kai,

Friday May 14 2021, Kai Richter wrote to Michael Dukelsky:

 MD>> https://github.com/huskyproject/hpt/wiki

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

 MD>> Here you talk about download.huskyproject.org.

 KR> No. At
 KR> https://github.com/huskyproject/hpt/wiki/hpt
 KR> is a rev date of dec 9, 2018.

Oh, I see.

 MD>> There is no sense to publish the documentation yearly, it is much
 MD>> better to publish it when it changes as it is now.

 KR> The latest local updates are done with the build/make update run. An
 KR> online publication is for people like me who are not on the latest
 KR> version. Yes, "me" are not many and maybe i'm the only one. On the
 KR> other hand there are many man pages available online. The idea for
 KR> yearly updates was to reduce the manual page updates but have a more
 KR> recent manual than from 2018.

 KR>>> text from the texi and edited it to ascii manually. Lazy as i am
 KR>>> the idea was to have quickly accessable file for reference.

 MD>> You are lazy? Oh, no! You spent much more time for editing texi,
 MD>> you could get the info-pages of the docs within a minute.

 KR> I would if it's that easy. But there is no makeinfo for my system. The
 KR> steps that are required to get it can't be done in a minure and would
 KR> be temporary. The "lazy" solution would be a system migration which is
 KR> already in progress but because of never touch a running system the
 KR> node is on the todo list with low priority. My actual situation is
 KR> like the two locations of the husky project, where github is active
 KR> and the sf net is still there.

OK, I understood you. Maybe the easiest way will be publishing docs in html and plain text via "GitHub releases".

Michael

... node (at) f1042 (dot) ru
--- GoldED+/LNX 1.1.5-b20180707