mono and snk key files

Christopher Brown snecklifter at gmail.com
Sun Dec 13 11:16:38 UTC 2009


2009/12/11 Adam Goode <adam at spicenitz.org>:
> On 11/29/2009 11:29 AM, Christopher Brown wrote:
>> 2009/11/29 Kalev Lember <kalev at smartlink.ee>:
>>> Hello,
>>
>> <snip>
>>
>>> Comments?
>>
>> I'm the maintainer for log4net but unfortunately not for nant. I've
>> finally gotten around to looking at this.
>>
>> Debian have a policy[1] of using a standard mono.snk which is provided
>> by a package (I guess we just then BuildRequires this) and I think
>> this seems like a good solution but have no experience of this.
>>
>
> We should definitely use Debian's key, right? Otherwise some Fedora CLI
> libraries would be unnecessarily incompatible with Debian, and whoever
> else uses Debian's key.
>
> The whole business of not shipping code-signing keys is a little
> contrary to open source. I think this is something that GPLv3 would
> prohibit. We should use a single well-known signing key for any package
> that we don't have the keys for, I think.

You're right.

This has already been resolved in devel by added mono.snk to the
mono-devel package. I'm just waiting on commit access to make the
required changes to F-11 and F-12 unless someone else wants to do it.

Best

-- 
Christopher Brown




More information about the devel mailing list