Subj : Huskydocs
To   : Michael Dukelsky
From : Kai Richter
Date : Fri May 14 2021 11:08:24

Hello Michael!

13 May 21, Michael Dukelsky wrote to Kai Richter:

 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.

No. At

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

is a rev date of dec 9, 2018.

 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.

The latest local updates are done with the build/make update run. An online publication is for people like me who are not on the latest version. Yes, "me" are not many and maybe i'm the only one. On the other hand there are many man pages available online. The idea for yearly updates was to reduce the manual page updates but have a more 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, you
 MD> could get the info-pages of the docs within a minute.

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

Regards

Kai

--- GoldED+/LNX 1.1.4.7
 * Origin:  Monobox  (2:240/77)

.