gluon/package/gluon-autoupdater/check_site.lua

need_string(in_site({'autoupdater', 'branch'}), false)

need_table({'autoupdater', 'branches'}, function(branch)
	need_alphanumeric_key(branch)

	need_string(in_site(extend(branch, {'name'})))
	need_string_array_match(extend(branch, {'mirrors'}), '^http://')
	need_number(in_site(extend(branch, {'good_signatures'})))
	need_string_array_match(in_site(extend(branch, {'pubkeys'})), '^%x+$')
	obsolete(in_site(extend(branch, {'probability'})), 'Use GLUON_PRIORITY in site.mk instead.')
end)
gluon-autoupdater: make site.conf branch setting optional Default to the alphabetically smallest branch if none is set in site.conf. Also prevent enabling the autoupdater when no branches exist. 2020-07-04 10:12:11 +00:00			`need_string(in_site({'autoupdater', 'branch'}), false)`
Validate site.conf 2014-07-05 00:48:56 +00:00
treewide: rework check_site_lib.lua In addition to significant internal differences in check_site_lib.lua (in particular unifying error handling to a single place for the upcoming multi-domain support), this changes the way fields are addressed in site check scripts: rather than providing a string like 'next_node.ip6', the path is passed as an array {'next_node', 'ip6'}. Other changes in site check scripts: * need_array and need_table now pass the full path to the sub fields to the subcheck instead of the key and value * Any check referring to a field inside a table implies that all higher levels must be tables if they exist: a check for {'next_node', 'ip6'} adds an implicit (optional) check for {'next_node'}, which allows to remove many explicit checks for such tables 2018-01-19 09:12:43 +00:00			`need_table({'autoupdater', 'branches'}, function(branch)`
			`need_alphanumeric_key(branch)`
Validate section names from site.conf in various packages 2015-10-11 17:31:44 +00:00
treewide: rework check_site_lib.lua In addition to significant internal differences in check_site_lib.lua (in particular unifying error handling to a single place for the upcoming multi-domain support), this changes the way fields are addressed in site check scripts: rather than providing a string like 'next_node.ip6', the path is passed as an array {'next_node', 'ip6'}. Other changes in site check scripts: * need_array and need_table now pass the full path to the sub fields to the subcheck instead of the key and value * Any check referring to a field inside a table implies that all higher levels must be tables if they exist: a check for {'next_node', 'ip6'} adds an implicit (optional) check for {'next_node'}, which allows to remove many explicit checks for such tables 2018-01-19 09:12:43 +00:00			`need_string(in_site(extend(branch, {'name'})))`
			`need_string_array_match(extend(branch, {'mirrors'}), '^http://')`
			`need_number(in_site(extend(branch, {'good_signatures'})))`
			`need_string_array_match(in_site(extend(branch, {'pubkeys'})), '^%x+$')`
build: add site check for obsolete settings (#1702) 2019-04-28 12:38:08 +00:00			`obsolete(in_site(extend(branch, {'probability'})), 'Use GLUON_PRIORITY in site.mk instead.')`
treewide: rework check_site_lib.lua In addition to significant internal differences in check_site_lib.lua (in particular unifying error handling to a single place for the upcoming multi-domain support), this changes the way fields are addressed in site check scripts: rather than providing a string like 'next_node.ip6', the path is passed as an array {'next_node', 'ip6'}. Other changes in site check scripts: * need_array and need_table now pass the full path to the sub fields to the subcheck instead of the key and value * Any check referring to a field inside a table implies that all higher levels must be tables if they exist: a check for {'next_node', 'ip6'} adds an implicit (optional) check for {'next_node'}, which allows to remove many explicit checks for such tables 2018-01-19 09:12:43 +00:00			`end)`