-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Marius Mauch wrote:
> Marius Mauch schrieb:
>> The first should be delayed until there is some consensus how the gpg
>> stuff should work in the future, the others I don't see the use for.
>> Also I only checked portage.py for changes, so emerge/repoman/... might
>> still have to be fixed.
>> Last but not least: I did some basic testing with this and the
>> important stuff seems to work, but I'm quite sure the code still has a
>> lot of bugs/issues, and this being a core functionality it needs a
>> *lot* of testing, so I'd really appreciate if you could all give it a
>> spin (but do not commit anything to the tree without manually checking
>> it first).
> 
> Does the lack of feedback (only got a reaction from Brian so far) mean
> that noone tried it or that it doesn't have any issues?

The patch applies and seems to work well.  At a quick glance the code looks pretty clean and it's nice to migrate more code out of portage.py to a separate module.  I've attached a refreshed version of the patch that applies cleanly against current svn (I've made no changes).

Zac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQFEGP1S/ejvha5XGaMRAl/7AJ9cZbjhWtjCz+ac2/tjQNUoivj0twCg7xAG
cYvDbMiqU5HtpNrVk7fs6RM=
=Eqlo
-----END PGP SIGNATURE-----