Subj : tparser with sample config
To   : Kai Richter
From : Michael Dukelsky
Date : Wed Apr 20 2022 11:07 am

Hello Kai,

Tuesday April 19 2022, Kai Richter wrote to Alle:

 KR> Fresh FreeBSD system, husky compiled with minimal conditions, sample
 KR> configs with "gmake en". hpt without parameters start with: "hpt/fbsd
 KR> 1.9 2022-02-08". Config path set, compiled and confirmed found by
 KR> tparser.

 KR> tparser/fbsd 1.9 2022-02-08
 KR> Test /home/test/husky/config for all modules
 KR> B 10:34:00   Enviroment variable [version] (used in config file
 KR> /home/test/husky/config) is not defined and is replaced with empty
 KR> string


 KR> Well, that's the default config. It's describtion is:

 KR> ##################################################################
 KR> # Main settings

 KR> # 'version' is one of predefined variables. It is set to husky
 KR> # version like MAJOR.MINOR.PATHLEVEL. We may want to check it
 KR> # first to eliminate problems with incompatible config and binaries.
 KR> if "[version]"=="1.9.0"
 KR> ###

 KR> I'm reading "It is set to..." that the setting is done already. But i
 KR> don't know where or if that's the designed intention.

The sample config was written by Nick Voronin in 2010. Maybe he wanted to implement the feature but he never did it. So in fact 'version' has no value in a configuration file.

 KR> Do i have to set the version by myself

What for? Do you want to write a config you will distribute?

 KR> or is it done by husky from
 KR> internal versions inside the modules?

No.

Michael

.... node (at) f1042 (dot) ru
--- GoldED+/LNX 1.1.5-b20180707
 * Origin: Moscow, Russia (2:5020/1042)

.