Required, Optional, and Never aren't to be mixed with the other settings.
The original version said this, but I thought the whole thing was getting
long winded, so I reworded it in a way that I thought would make this
implicit (guess not
Required, Optional, and Never will be sufficient for like 90% of users
(which is probably why they were the only options until recently), so I
separated them out from the more "advanced" settings (many people won't [and
shouldn't have to] know what e.g. marginally trusted signatures are).
On Jul 18, 2011 2:55 AM, "Allan McRae" <email@example.com> wrote:
> On 18/07/11 16:35, Kerrick Staley wrote:
>> The SigLevel config option replaces the VerifySig option, and has
>> similar semantics, but adds a set of advanced configuration options that
>> correspond to the recently introduced alpm_siglevel_t fields.
>> Signed-off-by: Kerrick Staley<firstname.lastname@example.org>
>> doc/pacman.conf.5.txt | 20 ++++++++++++++++++++
>> 1 files changed, 20 insertions(+), 0 deletions(-)
>> diff --git a/doc/pacman.conf.5.txt b/doc/pacman.conf.5.txt
>> index a28e00f..19cd6e3 100644
>> --- a/doc/pacman.conf.5.txt
>> +++ b/doc/pacman.conf.5.txt
>> @@ -156,6 +156,26 @@ Options
>> packages are only cleaned if not installed locally and not present in any
>> known sync database.
>> +*SigLevel =* ...::
> I was fairly sure previous the discussion indicated we would go with
> CheckLevel for the name of this.
> Anyway, I think it would be good to get a complete list of options
> sorted before documenting and implementing... Currently it seems
> Global options:
> Required (or Always?), Optional, Never - what about global controls for
> allowing marginal and unknown signatures.
> Also, we need to determine exactly how the suboptions will work. Do the
> PackageFoo options override global options? E.g. are these all
> equivalent (require database signatures but not package signatures)?
> CheckLevel = Required PackageOptional
> CheckLevel = Optional DatabaseRequired
> CheckLevel = DatabaseRequired PackageOptional