Created attachment 996081 [details] using CONFIG instead of CHROOT for --root option help/man Actially,this is not a bug. Just, it will be more user friendly to specify in help for mock: '-r CONFIG, --root=CONFIG' instead of '-r CHROOT, --root=CHROOT'.
Hmm that is question. You build in chroot. Chroot, which is defined by config file. So is it chroot or config. I tend to say "chroot name", which we obviously abbreviate just to "chroot".
Pros: 1. This is good abbreviate for example 'epel-5-x86_64.cfg' but not for '01_23_2015a1.cfg'. Building package for chroot name '01_23_2015a1' or building package with config '01_23_2015a1'? What if I have something like '--root /home/super/puper/builder/custom.cfg', is this consider to be 'CHROOT'? No. It seems to be PATH_TO_COFIG, or CONFIG. 2. Variances across the help. We have also option: '--configdir=CONFIGDIR' with description 'Change directory where config files are found'. Clearly and simply. No any confusion. No any '--configdir=CHROOTDIR'. This is using now in mock. Expecting the same for -r option. 3. Imagine, that patch of the distant past from RHBZ#452730 finally applied and made his developer really happy. And now we have '--root=CHROOT' and '--rootdir=DIRECTORY'. What's used for what? No way to easily understand until you read mindfully docs. This causes confusion. 4. The MOST important of pros. Simple usability test showed, that '-r CHROOT' cause confusion for new mock's users. Almost always for the first time usage they try to use -r option in a wrong way. For example, 'mock -r /path/to/chroot_build_dir xxx.src.rpm' or something like this.
Note that when using --uniqueext you can have multiple chroots per config. I agree with Mikhail that CONFIG is more descriptive.
Two vs. one. You won :) Commited as: * 89d7092 Use CONFIG instead of CHROOT in help/man for --root option [RHBZ#1197131]
mock-1.2.8-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/mock-1.2.8-1.fc22
mock-1.2.8-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/mock-1.2.8-1.fc21
mock-1.2.8-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/mock-1.2.8-1.fc20
mock-1.2.8-1.el7 has been submitted as an update for Fedora EPEL 7. https://admin.fedoraproject.org/updates/mock-1.2.8-1.el7
mock-1.2.8-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/mock-1.2.8-1.el6
Package mock-1.2.8-1.el7: * should fix your issue, * was pushed to the Fedora EPEL 7 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing mock-1.2.8-1.el7' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-6057/mock-1.2.8-1.el7 then log in and leave karma (feedback).
mock-1.2.8-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.2.8-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.2.8-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.2.10-1.el7 has been submitted as an update for Fedora EPEL 7. https://admin.fedoraproject.org/updates/mock-1.2.10-1.el7
mock-1.2.10-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/mock-1.2.10-1.el6
mock-1.2.10-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.2.10-1.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.