Grant, you will find a description in the manuals. As I said, you can choose. Cfengine doesn't do anything that you don't ask it to do. Cfengine 3 is a completely new animal, so don't begin by comparing it to 2. I would tyically say:
http://www.cfengine.org/manuals/cf3-reference.html#packages-in-agent-promises Grant Street wrote: > Hi Mark > > So does that mean that cfengine 3 will pass the version number of a > package through to the package manager? > > eg in cfengine 2 > in the repo there are the following packages > app-1.0 > app-2.0 > app-3.0 > > If I use the following > > packages: > app cmp=eq version=0:2.0 action=install > > cfengine 2 will only issue the following to install the package > > yum install app > > In doing so yum will install the most recent version ie version 3.0 > > all that would be required would be to issue > > yum install app-2.0 > > So to manage this not only do I have to have logic in cfengine, where it > should be, to define the version, I have to delete versions that are too > new or create separate repo's. When all else fails I have to resort to > command line rpm installs. This is what cfengine is meant to help with. > It already does something similar by passing x86_64/i386 through.... > > Anyway just trying to get an idea of the scale of the migration work. > cfengine has been great so far and has been great part of infrastructure. > > Grant > > On 07/10/10 15:11, Mark Burgess wrote: >> >> Cfengine 3 just gives you a generic interface to pass through to the >> package manager, So >> it's up to you to say what you want. I never specify version numbers, >> but some people want >> to. In some cases package managers give unwanted side effects like >> "smart" management of >> dependencies that can break stuff, but that's not a Cfengine issue. >> >> Grant Street wrote: >>> Hello >>> >>> We are currently on cfengine 2 and are looking to migrate to 3. One >>> issue we have is the the inability to install a particular rpm version >>> using the the package action. >>> >>> This causes us to "store" our current package versions by administering >>> the repo rather than just in the cfengine config files. Yum is more than >>> capable of installing a particular version from multiple on offer from >>> the repo. >>> >>> I just need to confirm if this is still the case in cfengine 3? It seems >>> that this is not fixed according to the docs below. >>> http://www.cfengine.org/manuals/cf3-reference.html#packages-in-agent-promises >>> >>> >>> thanks in advance >>> >>> Grant >>> _______________________________________________ >>> Help-cfengine mailing list >>> Help-cfengine@cfengine.org >>> https://cfengine.org/mailman/listinfo/help-cfengine >> > -- Mark Burgess ------------------------------------------------- Professor of Network and System Administration Oslo University College, Norway Personal Web: http://www.iu.hio.no/~mark Office Telf : +47 22453272 ------------------------------------------------- _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
