In an installer we have the option to specify some initial state and some children along with different spawnoptions for those children. The question is:
Should the installation or upgrade of a covenant accept any externally configured parameters ?
A danger is that users can be surprised that an application is different to how the covenant naturally behaves, and also a developer might not have coded for content in the chain that was not supplied by them. But some variables need to be different, like validator sets and the rootchain
We might choose to disallow these variables altogether.
We might always override all children with the top level parent.
Using @@INIT for any customization of the install might be better.
We might say that if you specify a covenant, then you cannot specify any children of that covenant in the installer, as that is required to be done by the covenant that you chose.
In an installer we have the option to specify some initial state and some children along with different spawnoptions for those children. The question is:
A danger is that users can be surprised that an application is different to how the covenant naturally behaves, and also a developer might not have coded for content in the chain that was not supplied by them. But some variables need to be different, like validator sets and the rootchain
We might choose to disallow these variables altogether. We might always override all children with the top level parent. Using
@@INITfor any customization of the install might be better. We might say that if you specify a covenant, then you cannot specify any children of that covenant in the installer, as that is required to be done by the covenant that you chose.