Forum: Cfengine Help Subject: Re: Cfengine Help: rather complex scenario (pkg install+configure - if necessary) Author: ticketo Link to topic: https://cfengine.com/forum/read.php?3,21559,21584#msg-21584
Thank you for your reply. It confirms my suspicion, that skipping the debconf stage completely is the way to go. However this is only part of the problem. As outlined in my OP I'm interested in some kind of dependency mechanism. What I'd like to achieve is a logic that goes something like this: a1) This is host "xyz" or even better a2) This is a hardware server with a LSI logic controller b) It needs the mpt-status package c) To install the package I need these "other" packages d) install and configure "other" packages e) install and configure mpt-status package I think it could be implemented if I decouple stuff. Bundle 1 - install mpt-status Bundle 2 - require installation of a suitable MTA Bundle 3 - configure postfix/exim/sendmail IF present Then either bundle 1 or bundle 2 would result in a MTA being present on the system and bundle 3 would be responsible to properly configure it. Does this sound reasonable? Are there better options? How would a cfengine expert tackle this problem? My main goal is to install a software package only on the hosts who actually need it - be it because of their function or because some other software requires it. But if it is installed then it has to be configured properly. What I don't want is to install a package on _all_ servers/hosts just because _some_ of them need it. _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
