[pacman-dev] [PATCH] [RFC] Add UpgradeSigLevel configuration option

Thomas Bächler thomas at archlinux.org
Thu Dec 22 05:53:38 EST 2011


Am 22.12.2011 11:26, schrieb Allan McRae:
> Use to override the global SigLevel value for upgrade operations.
> 
> e.g. when installing a package without a signature:
> 
> Fails to install:
> SigLevel = Optional
> UpgradeSigLevel = Required
> 
> Fails to install:
> SigLevel = Required
> 
> Installs:
> SigLevel = Required
> UpgradeSigLevel = Optional
> 
> Installs:
> SigLevel = Optional

I'll repeat some things that I said in the bug report - I have no idea
if this is feasible and should be done now:

I would love to distinguish between -U <local file> and -U <URL>. The
rationale is that I want automatically the highest security when I
download something (meaning: 'Required' for -U <URL>) but more
convenience when installing a local package that I build from AUR and
thus never signed (meaning: 'Optional' for -U <local file>).

If you think this is too hard for now, I think that this patch is better
than nothing.

Apart from that, I find the name UpgradeSigLevel confusing: People might
think it refers to upgrades in general, as opposed to the pacman
'upgrade' operation.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.archlinux.org/pipermail/pacman-dev/attachments/20111222/4de24bf4/attachment.asc>


More information about the pacman-dev mailing list