I'm trying to write a plugin to make it easier to manage packages on a
host. The basic idea is that each host has a per-host package that has
as it's requirements things I need the host to support.
ie:
foo.oppositelock.org-1.0-<epoch seconds>.noarch.rpm
requires:
httpd
sendmail
bind
This part is done. (per host packages generated automatically by rule,
added to a repository, etc)
The next part is to allow the per-host package to specify specific
versions, so that I can rollback a bad upgrade by pushing a new version
of the per-host package.
foo.oppositelock.org-1.0-<epoch seconds>.noarch.rpm
requires:
httpd=httpd-2.2.3-22.el5
sendmail=sendmail-8.13.8-2.el5
bind
This, obviously, has some issues; which is why I'm now fiddling with YUM
plugins.
So I've got a plugin that removes old versions of the per-host package,
so yum will only see the newest version of that package. As the next
trick, I'd like to get package downgrades to work correctly. I think
skip-broken like logic might help, but I'd need to not skip the
host-specific package (always try and upgrade that. Always).
Any suggestions for approach? Add skip-broken like logic to a post
resolve hook? Anything else I need to be aware of?
Doug
--
Doug Kilpatrick
kilpa...@oppositelock.org
_______________________________________________
Yum-devel mailing list
Yum-devel@lists.baseurl.org
http://lists.baseurl.org/mailman/listinfo/yum-devel
