-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm currently in the process of almost releasing a totally reworked Perl
module to handle GnuPG; it's based off the same IPC-style ( communication
via handles ) as my PGP::GPG::MessageProcessor, but it is more powerful
and better designed (in particular it can fully parse --with-colons
information and can create useful "Key" objects).
Since the interface and powerfulness do much more than "message
processing", I've been tempted to call it PGP::GnuPG::Interface.
However, the bareword "PGP" is not that good of a choice, I feel, because
it is used to relate to NAI's product, which this module does not support.
OpenPGP::GnuPG::Interface might be okay, but there is the fact that my
module itself doesn't implement OpenPGP; GnuPG does that for me.
However, "OpenPGP" is a new top-level CPAN directory, so I'm hesitant to
use this, as I plan putting it on CPAN.
Simply GnuPG::Interface also is an option, but once again, GnuPG is a new
top-level CPAN name.
If anyone has comments on these possible names, or has good suggestions,
please let me know.
- --
Frank Tobin http://www.uiuc.edu/~ftobin/
"To learn what is good and what is to be valued,
those truths which cannot be shaken or changed." Myst: The Book of Atrus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (FreeBSD)
Comment: pgpenvelope - http://pgpenvelope.sourceforge.net/
iEYEARECAAYFAjjy6H8ACgkQVv/RCiYMT6M4kQCeJrdMr1qyQem8jPSgogH8BksF
7iYAnR0qJAJtUatscxz6ygS2aQS8Ca3h
=unT3
-----END PGP SIGNATURE-----
Hash: SHA1
I'm currently in the process of almost releasing a totally reworked Perl
module to handle GnuPG; it's based off the same IPC-style ( communication
via handles ) as my PGP::GPG::MessageProcessor, but it is more powerful
and better designed (in particular it can fully parse --with-colons
information and can create useful "Key" objects).
Since the interface and powerfulness do much more than "message
processing", I've been tempted to call it PGP::GnuPG::Interface.
However, the bareword "PGP" is not that good of a choice, I feel, because
it is used to relate to NAI's product, which this module does not support.
OpenPGP::GnuPG::Interface might be okay, but there is the fact that my
module itself doesn't implement OpenPGP; GnuPG does that for me.
However, "OpenPGP" is a new top-level CPAN directory, so I'm hesitant to
use this, as I plan putting it on CPAN.
Simply GnuPG::Interface also is an option, but once again, GnuPG is a new
top-level CPAN name.
If anyone has comments on these possible names, or has good suggestions,
please let me know.
- --
Frank Tobin http://www.uiuc.edu/~ftobin/
"To learn what is good and what is to be valued,
those truths which cannot be shaken or changed." Myst: The Book of Atrus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (FreeBSD)
Comment: pgpenvelope - http://pgpenvelope.sourceforge.net/
iEYEARECAAYFAjjy6H8ACgkQVv/RCiYMT6M4kQCeJrdMr1qyQem8jPSgogH8BksF
7iYAnR0qJAJtUatscxz6ygS2aQS8Ca3h
=unT3
-----END PGP SIGNATURE-----