Is there a "mock" setup or downloadable list of tweaked packages for testing CentOS 6 builds?
I may be able to pry time free to test CentOS 6 builds. But I don't want to burn useful worktime with building mock files and manually rebuilding all the SRPM's. I've got access to licensed RHEL 6 to use as a build environment, and to do what gcc does: build a "staging" setup, then do a clean rebuild with that staging, then do a final rebuild to make sure material matches and look for discrepancies.
Is this already done somewhere I can get a copy, so that I don't have to burn time re-inventing the wheel? I'd particularly like to make sure that a current "mock" is in the "extras" repository, to speed build times. (The current mock in epel-testing is much faster and more efficient than the older mock releases.)
On 01/06/2011 01:12 PM, Nico Kadel-Garcia wrote:
sure that a current "mock" is in the "extras" repository, to speed build times. (The current mock in epel-testing is much faster and more efficient than the older mock releases.)
if the epel mock works for you, why not use it ? its just a case of pointing the repo's to your local storage.
- KB
On Thu, Jan 6, 2011 at 9:29 AM, Karanbir Singh mail-lists@karan.org wrote:
On 01/06/2011 01:12 PM, Nico Kadel-Garcia wrote:
sure that a current "mock" is in the "extras" repository, to speed build times. (The current mock in epel-testing is much faster and more efficient than the older mock releases.)
if the epel mock works for you, why not use it ? its just a case of pointing the repo's to your local storage.
I do. I'm urging an upgrade for the benefit of other mock users still using CentOS's package, unaware of the benefits of the EPEL release, and for the benefits of the CentOS repository build procedures.
On 01/06/2011 10:17 PM, Nico Kadel-Garcia wrote:
I do. I'm urging an upgrade for the benefit of other mock users still using CentOS's package, unaware of the benefits of the EPEL release, and for the benefits of the CentOS repository build procedures.
CentOS-4 and 5 are built using the mock-0.6 packages, thats unlikely to change unless there is a good reason - speed / performance wins on desktop machines with low resource levels are are not a good reason. Sticking with the process that works and does what it needs to in a reliable manner is worth a lot more. Of course, there are things that are important from the distro perspective, you are welcome to use whatever your site preferences might be.
For CentOS-6, yes were going to clearly need a more recent mock. If you are building for c6 now, use the epel packages that should be a good base to develop from.
- KB
On Thu, Jan 6, 2011 at 2:33 PM, Karanbir Singh mail-lists@karan.org wrote:
For CentOS-6, yes were going to clearly need a more recent mock. If you are building for c6 now, use the epel packages that should be a good base to develop from.
I just talked with Steve Tindall (one of the elrepo people). He wanted to remind people that mock-1.1.6 is available in el5/rpmforge-testing and it runs well on el5 and el6. mock 1.1.6 outputs very useful diagnostic info on failed builds.
Akemi
On Thu, Jan 06, 2011 at 05:22:10PM -0800, Akemi Yagi wrote:
On Thu, Jan 6, 2011 at 2:33 PM, Karanbir Singh mail-lists@karan.org wrote:
For CentOS-6, yes were going to clearly need a more recent mock. If you are building for c6 now, use the epel packages that should be a good base to develop from.
I just talked with Steve Tindall (one of the elrepo people). He wanted to remind people that mock-1.1.6 is available in el5/rpmforge-testing and it runs well on el5 and el6. mock 1.1.6 outputs very useful diagnostic info on failed builds.
1.1.8 was just released and failure output was further improved with that version.
regards,
Florian La Roche
On Thu, Jan 6, 2011 at 9:58 PM, Florian La Roche Florian.LaRoche@gmx.net wrote:
On Thu, Jan 06, 2011 at 05:22:10PM -0800, Akemi Yagi wrote:
I just talked with Steve Tindall (one of the elrepo people). He wanted to remind people that mock-1.1.6 is available in el5/rpmforge-testing and it runs well on el5 and el6. mock 1.1.6 outputs very useful diagnostic info on failed builds.
1.1.8 was just released and failure output was further improved with that version.
That's very nice to know. Thanks for the note.
Akemi
-
Akemi Yagi -
Florian La Roche -
Karanbir Singh -
Nico Kadel-Garcia