mock rfe - buildgroup

[Michael E Brown]

On Fri, Jul 06, 2007 at 05:50:31PM -0400, Jesse Keating wrote:
> On Friday 06 July 2007 17:32:49 Jeff Sheltren wrote:
> > For example, I have not changed defaults.cfg at all, but all of the  
> > fedora-*, redhat-*, epel* configs do have local modifications.  Now,  
> > if you push a defaults.cfg file which is blank, that will cause my  
> > unedited defaults.cfg to be overwritten.  Once that happens, all of  
> > the other mock configs will be trying to do 'groupinstall buildsys-
> > build' which is a non-existent group (except apparently in rawhide).
> >
> > I would much prefer if the default install command remained the same  
> > for the time being and the change would only be made in the  
> > development config.
> 
> Jeff, this is on a rawhide box you're talking about?  I think we're only going 
> to make the change in rawhide and not further down the stack.

Jesse,
    I've been updating FC6/7 and EPEL4/5 with every release. If we do
this change and dont want to push it to the older releases, then we
would need to branch mock, and this seems like too trivial a change to
do all that work for.

    I think that my current repo at http://linux.dell.com/git/mock.git
has everything we need to make everything nicely forward and backward
compatible:

    Here is what I have done:

1) update all individual config files with the chroot_setup_cmd
2) mock.py still defaults to 'install buildsys-build'
3) defaults.cfg is now empty and reserved for site-local changes

    This means that anybody who has any site-local changes to any of
their config files with get the updated configs as .rpmnew files. Their
existing configs will continue to work, as we have not changed the
defaults. They can then update the config files to include the
chroot_setup_cmd at their leisure.

Todo for $nextrelease:
1) update mock.py so that 'groupinstall buildsys-build' is the new
default.

--
Michael