On Tue, 2010-12-07 at 15:26 -0500, seth vidal wrote: > On Mon, 2010-12-06 at 20:57 -0500, Josh Boyer wrote: > > Hi All, > > > > I have been looking at the 'yum-ppc64-preferred.patch' in the RHEL6 > > yum package[1] lately, and I've been thinking about how to make this a > > bit more configurable. I've not done much python coding and even less > > yum coding, so I was hoping to get a few opinions on approaches to > > make this suitable to upstream (maybe). > > > > My initial thought was a yum plugin, however given that the code in > > question is in the rpmUtils module and there are no slot points that I > > can see that would allow similar modifications, I don't think that > > will work. (Though I do see a FIXME in readMainConfig for basearch). > > > > The next idea was to make a new config option in the core yum code > > that would set the appropriate items and could be passed to the > > getBestArch and getBaseArch functions. I added a similar option to > > the Fedora mash tool, but it is specific to ppc64 (perfer_ppc64 is the > > name). Would something like that be suitable, or would the option > > need to be more generic so that it could work for sparc64 (or other > > arches) as well? > > > > Any direction would be appreciated. > > okay the bestarch/basearch/compatarch stuff: > > here's what has to happen - all of this needs to be in the archstorage > class. That way it can be redefined in runtime w/o worrying about what > it was elsewhere. > > So the trick is going through yum and finding all the places we refer to > these functions and making them use similar results/items from > ArchStorage() > > I think I'd be happy with a patch like that. It seems clean and > consistent w/what else we're doing. > > James, what do you think?
Yeh, I'm fine with it ... although we then need some way to "configure" the results. Which I guess we do around "yb.conf" init. time. _______________________________________________ Yum-devel mailing list [email protected] http://lists.baseurl.org/mailman/listinfo/yum-devel
