Hello,
I've had mdpolicy=group:primary set for all yum-based distros in my local mock configs for quite a while. I suppose it would be a good default as AFAIK mock has no use for updateinfo or pkgtags metadata, and groups metadata is only used during initial chroot setup if the cmd contains a group, and it's downloaded whenever needed even with mdpolicy set to group:primary.
Can anyone think of a reason why this wouldn't be a good idea in all yum-based configs shipped with mock (epel-*.cfg, fedora-22-*.cfg, fedora-23-*.cfg)? If not, I'll push this soon.
On Fri, 11 Dec 2015 17:14:39 +0200 Ville Skyttä ville.skytta@iki.fi wrote:
Hello,
I've had mdpolicy=group:primary set for all yum-based distros in my local mock configs for quite a while. I suppose it would be a good default as AFAIK mock has no use for updateinfo or pkgtags metadata, and groups metadata is only used during initial chroot setup if the cmd contains a group, and it's downloaded whenever needed even with mdpolicy set to group:primary.
Can anyone think of a reason why this wouldn't be a good idea in all yum-based configs shipped with mock (epel-*.cfg, fedora-22-*.cfg, fedora-23-*.cfg)? If not, I'll push this soon. -- buildsys mailing list buildsys@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/buildsys@lists.fedoraproject.org
Makes sense to me. I'd say let's try it on a wider set of configurations and see if anything breaks.
Clark
On Fri, Dec 11, 2015 at 7:52 PM, Clark Williams clark.williams@gmail.com wrote:
On Fri, 11 Dec 2015 17:14:39 +0200 Ville Skyttä ville.skytta@iki.fi wrote:
Hello,
I've had mdpolicy=group:primary set for all yum-based distros in my local mock configs for quite a while. I suppose it would be a good default as AFAIK mock has no use for updateinfo or pkgtags metadata, and groups metadata is only used during initial chroot setup if the cmd contains a group, and it's downloaded whenever needed even with mdpolicy set to group:primary.
Can anyone think of a reason why this wouldn't be a good idea in all yum-based configs shipped with mock (epel-*.cfg, fedora-22-*.cfg, fedora-23-*.cfg)? If not, I'll push this soon.
Makes sense to me. I'd say let's try it on a wider set of configurations and see if anything breaks.
Ok, I've pushed this to make it easier to test.
buildsys@lists.fedoraproject.org