--===============1857788463==
Content-Type: multipart/alternative; 
	boundary="----=_Part_12030_10047607.1189509627182"

------=_Part_12030_10047607.1189509627182
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I've enabled the gpg checking in SVN

The auto generated recipes dont seem to validate with probonos gpg key
though.

Most of the code is a direct port from zero install, not sure how to add new
keys yet....

To test I just installed the key using seahorse

Note if there is no sig on the recipe then it checks URLs

We can register the autogen key at install time but we will need some way to
add new ones, ie for custom recipies

Ideas?

Zero install has a complete key mangement system... if we could make things
simpler it would be good

Cheers

Killerkiwi

------=_Part_12030_10047607.1189509627182
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I&#39;ve enabled the gpg checking in SVN<br><br>The auto generated recipes dont seem to validate with probonos gpg key though.<br><br>Most of the code is a direct port from zero install, not sure how to add new keys yet....
<br><br>To test I just installed the key using seahorse<br><br>Note if there is no sig on the recipe then it checks URLs<br><br>We can register the autogen key at install time but we will need some way to add new ones, ie for custom recipies
<br><br>Ideas? <br><br>Zero install has a complete key mangement system... if we could make things simpler it would be good<br><br>Cheers<br><br>Killerkiwi<br>

------=_Part_12030_10047607.1189509627182--

--===============1857788463==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
klik-devel mailing list
klik-devel@kde.org
https://mail.kde.org/mailman/listinfo/klik-devel

--===============1857788463==--