On Friday 17 Sep 2010 10:15:13 Mark Burgess wrote: > > The documentation says "Package promises are like commands promises in > > the sense that cfengine promises nothing about the outcome of executing > > a command. All it can promise is to interface with it, starting it and > > using the results in good faith. Packages are basically `outsourced', to > > invoke IT parlance." > > > > As I read it, "using the result in good faith" should mean "trust the > > command", including its exit status, which is also (imho) the only > > possible sensible policy, short of building package management into > > cfengine. > > David, the problem is one of semantics. In bulk operations, some things > succeed and some fail. You are entirely slave to the behaviour of the > package manager, making it difficult to have a consistent behaviour that > everyone can agree on. Installing one by one is inefficient, but possible. > > Try to think more about the final (desired) state rather than the outcome > of the shell command.
I see your point, but then what about adding an option eg trust_exit_status => "true" or something like that to package promises, to make it do what I was expecting? Then people could choose. -- D. _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
