Mailing List Archive

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

On Tue, 17 Nov 1998, Thomas Mikkelsen wrote:
> Should gpg come with its own frontends: Im am thinking about something
> like the gnucash project where you can choose between several frontends.
> How does "./configure --enable-gnome" or "configure --enable-kde" sound
> to you.

I'd actually suggest that this remain separate. You really don't want to
start wars about whether having a KDE frontend bundled with an
FSF-copyrighted project is a good idea, or arguments over why desktop 'n'
or toolkit 'm' isn't supported, for infinite values of 'n' and 'm' (GTK+,
QT, curses, OS/2, BeOS, Win32, Gnome, KDE, ad infinitum).

Also, while building frontends is certainly a nice idea, bundling them
with the core package won't keep them maintained; only active interest in
maintaining them will do that.

Finally, GPG is a utility, unlike GNUCash, which is an end-user
application. There's a pretty substantial difference here.

I'd vote to keep it out of the core GPG distribution. This doesn't mean
I'm against a frontend (I actually rather like GnomePGP), but that I'm
against bundling it with the GPG core set, and think that it should be
maintained separately, as an end-user app.

Just MHO, of course, and subject to change. ;-)

- --
Edward S. Marshall <emarshal@logic.net> /> Who would have thought that we -o)
http://www.logic.net/~emarshal/ // would be freed from the Gates of /\\
Linux Weenie, Open-Source Advocate </ hell by a penguin named "Tux"? _\_v
-----BEGIN PGP SIGNATURE-----
Version: GNUPG v0.4.3 (GNU/Linux)
Comment: For info finger gcrypt@ftp.guug.de

iEYEARECAAYFAjZSJMcACgkQod/ZJKejQQryWQCcCRfdSZBZ0lMMVR4WHHrMhA0p
pqgAoIZ44Cu0dnA6yI8XtWKJOB71DNZO
=YgQW
-----END PGP SIGNATURE-----

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

On Tue, 17 Nov 1998, Edward S. Marshall wrote:

>On Tue, 17 Nov 1998, Thomas Mikkelsen wrote:
>> Should gpg come with its own frontends: Im am thinking about something
>> like the gnucash project where you can choose between several frontends.
>> How does "./configure --enable-gnome" or "configure --enable-kde" sound
>> to you.

Hmm...however, there's (bound to be) more than one KDE or Gnome PGP/GPG/Crypto
package. There's GnomePGP, kpgp, kcmpgp, and I'm trying to write kPGPShell
(way, WAY alpha, barely makes menus...). And with the exception of GnomePGP,
the others aren't really working. And it would take even more time to get
good, working KDE *and* Gnome *and* non-KDE/non-Gnome (because some are going
to want this) graphicals GPGs than if other, independant people worked with
Werner to make sure that their programs worked with his (like I sometimes do
when it don't work for me, although now that I can compile it, I'm happy...)

>Also, while building frontends is certainly a nice idea, bundling them
>with the core package won't keep them maintained; only active interest in
>maintaining them will do that.

I definitely have to agree - GPG only comes out with a new version once in a
while, whereas I come out with new revisions of pgp4pine at least weekly,
usually everyother day or so.

Also, FYI, the key I signed this with IS time-limited because GPG is beta
software, so I'm not doing any lengthy keys yet (soon, maybe).

Chris Wiegand

'If Bill Gates had a dime for every time Windows crashed...
... Oh wait a minute, he already does...' - Anonymous

Linux \'lih-nucks\ n.: Antidote to the computer viri known as Windows.

-----BEGIN PGP SIGNATURE-----
Version: GNUPG v0.4.2 (GNU/Linux)
Comment: For info finger gcrypt@ftp.guug.de

iEYEARECAAYFAjZScK4ACgkQnvdM/T08bnkLdACeKM7HVyDeKnyLJCdl46Jd/9GW
O2gAoJKrbUmY1sHCzl9BfGlnV7lB5VC/
=tRRR
-----END PGP SIGNATURE-----

Christopher Wiegand <cwiegand@urgentmail.com> writes:

> good, working KDE *and* Gnome *and* non-KDE/non-Gnome (because some are going
> to want this) graphicals GPGs than if other, independant people worked with
> Werner to make sure that their programs worked with his (like I sometimes do

I recently added a whole bunch of code to GnuPG to support Max's
GomePGP but he never used this and he virtually vanished from the net
(maybe due to some Russian financial crisis and expensive Internet
access?)

> I definitely have to agree - GPG only comes out with a new version once in a
> while, whereas I come out with new revisions of pgp4pine at least weekly,
> usually everyother day or so.

Yes, we should keep them separate.

> Also, FYI, the key I signed this with IS time-limited because GPG is beta
> software, so I'm not doing any lengthy keys yet (soon, maybe).

No problem: The key expiration time is bound to the signature and you
can change it at anytime without problems.


Werner