Description of problem:
support --gpgcheck=0 option with commandline
Version-Release number of selected component (if applicable):
[I'd actually like it to work with yum-2.2 - aka fc3 but..]
Its painful to always edit config files to set this flag. Is required esp if one
wants to do:
yum --gpgcheck=0 localinstall foobar.rpm
One potential issue is - here I might just want gpgcheck to be disabled just for
this one rpm - but not any dependent packages that might be needed [from other
So - perhaps we need 2 options here.
No. I think that this will be a confusing set of command line arguments for
users. If you want to have this option available for yourself I'd encourage you
to look at the plugin infrastructure available in yum 2.3.X
if you want to enable/disable gpgchecking for local packages set gpgcheck=0/1 in
your yum.conf under [main]
if you want to enable/disable gpgchecking for packages in repositories set
gpgcheck=0/1 in the repository definition either in your yum.conf or in the
setting gpgcheck options for repositories is fine. It works [and I use it]
But it does not work for 'localinstall' [without editing config files]. I
believe there is a good reason for the 'localinstall' option - and I'm hoping
you can support toggling gpgcheck for this usage.
If one were to edit config files - one could also use local repositories - and
not use the 'localinstall' option.
This would be particularly handy for, say, the JPackage java RPMs that users
have to build for themselves. I'm currently putting together a detailed HOWTO
for this, and it would be much nicer to be able to say:
# yum --gpgcheck=0 localinstall java*.rpm
than to tell them to edit their yum.conf (which, properly, defaults to
gpgcheck=1), do the localinstall and then edit the yum.conf back again.
I think this command does have its use cases on rare occasions. It probably
should be added with a strong warning to import the gpg key instead if applicable
this can now be implemented by a plugin. So I'm going to close this - but there
is potential for this to be implemented in a later release, maybe.