On 05/31/2011 09:14 AM, Owen Beckley wrote: >> [email protected]] On Behalf Of Wes Hardin >> Sent: Monday, May 30, 2011 11:23 AM >> On 05/27/2011 11:34 PM, Christian Horn wrote: >>> On Fri, May 27, 2011 at 01:21:14PM -0500, Owen Beckley wrote: >>>> >>>> I was wondering if there is an automated way to have a repo > included >> in >>>> cobbler, but have it be disabled by default when it's listed in >>>> /etc/yum.repos.d/cobbler-config.repo. >>> >>> - disable it in %post with a line of sed >>> >>> The only downside I see is if you list packages in %packages that > are >>> more current in your 'optional' repo they will be fetched from > there. >> >> Depending on how broad you want the "disabled-ness" to be, it's could >> even >> easier than that. Inside each repo directory, there is a file called >> "config.repo" that is the template for what ends up Cobbler generated >> cobbler-config.repo. You can simply change the "enabled" line there >> and all >> > > This gets me half way. The repo in question ends up disabled in > /etc/yum.repos.d, but is still listed in the expansion of > $yum_repo_stanza. > > Should I request a new feature?
Ah yes, I don't deploy RHEL5 or newer widely yet, so I don't use and didn't catch the subtle difference of $yum_repo_stanza. Certainly sounds like a worthwhile enhancement to me. I'd considered making the request myself for a checkbox in the web GUI to disable a repo but the config.repo edit was a simple enough workaround for my use. -- /* Wes Hardin */ UNIX/Linux Systems Administrator, IT Engineering Support Maxim Integrated Products: Innovation Delivered _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
