> This part sounds like it'll work well then, but I'm not sure about the
change in release upgrade behaviour above.
Good point !
What about "Breaks:" instead of "Recommends:" ?
Package A breaks Package B when both packages cannot be simultaneously configured in a system. The package management system will refuse to install one if the other one is already installed and configured in the system.
> In comment #20, you said that there doesn't seem to be a way to disable
DDNS at runtime in Trusty. But this is presumably based on the
upstream-shipped build configuration. How difficult would it be to do by
patching the code?
Disabling the feature at runtime would definitely be a good alternative. I don't think it will be easily doable without doing some important modification in the src code as AFAIK we can't disable/enable a preprocessor option at runtime.
The C preprocessor modifies a source code file before handing it over to the compiler.
> This part sounds like it'll work well then, but I'm not sure about the
change in release upgrade behaviour above.
Good point !
What about "Breaks:" instead of "Recommends:" ?
Package A breaks Package B when both packages cannot be simultaneously configured in a system. The package management system will refuse to install one if the other one is already installed and configured in the system.
> In comment #20, you said that there doesn't seem to be a way to disable
DDNS at runtime in Trusty. But this is presumably based on the
upstream-shipped build configuration. How difficult would it be to do by
patching the code?
Disabling the feature at runtime would definitely be a good alternative. I don't think it will be easily doable without doing some important modification in the src code as AFAIK we can't disable/enable a preprocessor option at runtime.
The C preprocessor modifies a source code file before handing it over to the compiler.