On Fri, Jul 06, 2007 at 03:53:08PM -0400, Jeff Sheltren wrote: > >>I see two (three?) ways to handle this: > >> > >>1) only add this line to -devel. > >> > >>2) change the default in mock.py, and override F7/F6/EPEL4/EPEL5 > >>configs. > >> > >>3) add this line to -devel, and then migrate it to (2) above after a > >>period of time (perhaps when we drop F6?) > > > >Yeah, I had this fleeting thought when I was doing it, then > >promptly forgot > >about it. One of those days... > > > >I think 2 is probably safest, if people have locally modified their > >configs, > >but I was also thinking we'd only make this change in rawhide, so > >it would > >only be rawhide people who get it, not pushing it out to existing > >Fedora/RHEL > >setups, so 3 is probably fine too. > > > > I'm confused why you would say (2) is the safest. Overriding the > default would cause all those who use modified config files to fix > them when mock gets updated.
When we update defaults.cfg, everybody with local modifications is broken until they manually make the change. I dont like breaking people's configs. > My order of preference for the above options would be (1), (3), (2). > In fact, if you go with (3), it makes sense to me to change the > default after F7 is dropped rather than FC6. F7 continues to use a > buildgroups repo/RPM, correct? Yes, but at that point, F7 becomes one single config override, and is easier to manage than everything being an override. My preference is still 2. -- Fedora-buildsys-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
