<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.5.6"> </HEAD> <BODY> <BLOCKQUOTE TYPE=CITE> <PRE> > > I could easily add virtual provides support into 'yum install' in > cvs-HEAD and this problem goes away - I'm just wondering would it make > more sense to hack yum to make it comply with mach2 or to hack mach2 to > make it work with yum. You mean "hack mach to make it work with yum" as in "import yum..." kind of thing? If so, I think that's far better approach than invoking it from through command line with all the overhead of re-re-re-reading in metadata etc - it'd not only improve speed but give far more control over things. Regardless of that, supporting virtual provides in 'yum install' would be a nice little addition to yum anyway. </PRE> </BLOCKQUOTE> okay I added in the virtual provides to yum install options. It's just sorta hacked in right now it needs to be abstracted and cleaned up a bit, but it does what you'd expect and takes all sorts of whacked out things like: yum install "foo > 1.1" yum install "foo == 1.1" yum install "foo = 1.1" (same as above) yum install "foo < 1.1" <=, >= are also taken. != is not accepted and don't make me slap anyone who asks. :) etc etc etc. its only an option to install atm, though, not to update, for obvious reasons so yum 2.3.1 should work just fine with mach for what it wants to do. -sv </BODY> </HTML>