Yes, this will work around for now. What version of SuSE are you running. Yast is a waste of space, but zypper is pretty good since version 11.1 It can handle local media or remote repositories.
Diego Zamboni wrote: > Hi Mark, > > On Wed, Jan 13, 2010 at 8:49 PM, Mark <[email protected]> wrote: >> You are correct. This never got implemented as everyone seems to be using >> yum or some such repos these days. We can come cack to this in the next >> weeks. > > Thanks for the reply. I am wondering now what do people use to manage > software using cfengine on SuSE machines? I've done some searches but > haven't found anything that interfaces properly with yast, for > example. In my case, the package in question is an internal one that > is not available in the repositories, hence the need to install it > from a file (I guess a proper solution would be to set up an internal > repository and use yast, but since it's only one package, it seems > overkill for now). > > The workaround that I found is to specify the full path as part of > package_name_convention: > > package_name_convention => > "${localpackagefiles}/$(name)-$(version).$(arch).rpm"; > > This works fine for now, but I guess it would break if I try to do any > operation besides "add", since it will try to use the full path for > all operations (e.g. remove packages). > > Best regards, > --Diego > _______________________________________________ > Help-cfengine mailing list > [email protected] > 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 [email protected] https://cfengine.org/mailman/listinfo/help-cfengine
