I have repos set up for the base system and also the "built" packages. Instead of manually commenting these out when the need arises, it can automatically be scripted using the --disablerepo option to mock. This is then forwarded to the yum command.
enjoy,
On Thu, 2005-09-29 at 11:31 +0800, Jeff Pitman wrote:
I have repos set up for the base system and also the "built" packages. Instead of manually commenting these out when the need arises, it can automatically be scripted using the --disablerepo option to mock. This is then forwarded to the yum command.
enjoy,
why would we need to add this option to mock? Is it terribly common to need to disable a repo for some specific package build? Why not just have another config file?
-sv
On Thursday 29 September 2005 12:40, seth vidal wrote:
why would we need to add this option to mock? Is it terribly common to need to disable a repo for some specific package build? Why not just have another config file?
Ties into the obsoletes question I had on the yum list. With "built" in the config, then I cannot init a chroot. So, it's common in that I need it when the root gets re-initialized. But, if mock's only target audience is FE, then I guess it doesn't matter that much since FE doesn't participate in the cardinal sin of updating Core packages (or worse: renaming them :D).
Another config file would work; but, I guess the same argument could be used for yum itself, too: Why not just have another config file in yum?
Anyway, patch is FYI. No expectations for upstream adoption. (I realize that feature rot needs to be reigned upon.)
thanks,
buildsys@lists.fedoraproject.org
-
Jeff Pitman -
seth vidal