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

[Florian Pritz]

On 13.01.2012 02:30, Allan McRae wrote:
> On 22/12/11 20:26, Allan McRae wrote:
>> 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
>> 
>> Signed-off-by: Allan McRae <allan at archlinux.org>
>> ---
>> 
>> The main issue I see here is that UpgradeSigLevel must come after the global
>> SigLevel value.  Otherwise the only way I see to use the value of SigLevel as
>> a default for UpgradeSigLevel requires much code duplication.
> 
> 
> So, any further comments on this before I take a stab at improving
> things further.  So far the comments were:
> 
> 1) distinguish between "pacman -U <url>" and "pacman -U <file>"
> 2) change name of option as "Upgrade" is confusing
> 
> What about using:
> LocalFileSigLevel
> RemoteFileSigLevel
> 
> Is RemoteFile too confusing with packages from repos?

Yes. Even in this context I wondered for a moment if that applies to -S
as well, but then I guess you will keep SigLevel for that.

UpgradeSigLevel is also confusing because that should/could/might apply
to -Su, but not -S. This (wrong idea) would even make sense right now
because not all old packages are signed, but all new ones are.

-- 
Florian Pritz

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.archlinux.org/pipermail/pacman-dev/attachments/20120113/894e6cc5/attachment-0001.asc>