Gnus development mailing list
 help / color / mirror / Atom feed
From: Daiki Ueno <ueno@unixuser.org>
To: Reiner Steib <Reiner.Steib@gmx.de>
Cc: ding@gnus.org,  Miles Bader <miles@gnu.org>
Subject: Re: pgg-gpg doesn't work at all [fix included]
Date: Sun, 29 Jul 2007 17:03:37 +0900	[thread overview]
Message-ID: <88142c4a-390e-44e8-b39f-b37b59f1fee7@well-done.deisui.org> (raw)
In-Reply-To: <4e687c1c-a602-4248-a49f-535fa0372646@well-done.deisui.org> (Daiki Ueno's message of "Sun, 29 Jul 2007 03:18:35 +0900")

Sorry for consecutive posts.

>>>>> In <4e687c1c-a602-4248-a49f-535fa0372646@well-done.deisui.org> 
>>>>>	Daiki Ueno <ueno@unixuser.org> wrote:
> > We want to sync Gnus trunk with Emacs trunk.  If EasyPG should become
> > the default sign and encryption support in Gnus (obsoleting PGG) ---
> > and as I understand this is your suggestion ---,

"the default" is somewhat confusing phrase.  I'd suggest that EasyPG
should become "the preferred" sign and encryption support in Gnus.
i.e. Gnus will use it rather than PGG, if available.

Anyway,

> > we should have the EasyPG package included in both Gnus trunk and
> > Emacs trunk.

I don't think so.  IIUC, you can suppose the following use cases:

(a) Emacs 21/22 (release)
(b) Emacs 21/22 (release) + Gnus CVS
(c) Emacs CVS + Gnus CVS

The users who benefit from including EasyPG in Gnus CVS are, using (b)
and too lazy to install EasyPG as a separate package.  I assume that
they are in the minority compared to others[1].  Is it not enough to
display warning messages when PGG is going to be used instead of EasyPG?

Regards,

Footnotes: 

[1] Yes, I'm aware of several OS distributions which have Gnus packages
built from Gnus CVS.  However, they are not in the case because EasyPG
is also packaged there and dependencies between packages can be
asserted).
-- 
Daiki Ueno



  reply	other threads:[~2007-07-29  8:03 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-25 10:15 Michael Sperber
2007-07-25 10:44 ` Daiki Ueno
2007-07-25 10:55   ` Michael Sperber
2007-07-25 12:18   ` Sascha Wilde
2007-07-25 12:40     ` Daiki Ueno
2007-07-25 17:40       ` Leo
2007-07-26  0:21         ` Miles Bader
2007-07-26  0:43           ` Daiki Ueno
2007-07-26  1:00             ` Miles Bader
2007-07-26 21:16           ` Reiner Steib
2007-07-26 23:53             ` Daiki Ueno
2007-07-28 15:22               ` Reiner Steib
2007-07-28 18:18                 ` Daiki Ueno
2007-07-29  8:03                   ` Daiki Ueno [this message]
2007-08-31  9:33                   ` PGG and EasyPG (was: pgg-gpg doesn't work at all [fix included]) Reiner Steib
2007-08-31 10:21                     ` Reverting PGG to v5-10 code base on the trunk (was: PGG and EasyPG) Reiner Steib
2007-10-03 13:59                       ` Reverting PGG to v5-10 code base on the trunk Reiner Steib
2007-10-03 14:17                         ` Simon Josefsson
2007-08-31 14:13                     ` PGG and EasyPG (was: pgg-gpg doesn't work at all [fix included]) Daiki Ueno
2007-09-03 21:36                       ` Leo
2007-09-04  7:00                         ` Daiki Ueno
2007-09-04  7:20                           ` Leo
2007-07-26 21:27     ` pgg-gpg doesn't work at all [fix included] Reiner Steib

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=88142c4a-390e-44e8-b39f-b37b59f1fee7@well-done.deisui.org \
    --to=ueno@unixuser.org \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@gnus.org \
    --cc=miles@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).