From: Michael Albinus <michael.albinus@gmx.de>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: auth-source.el and eieio
Date: Mon, 14 Feb 2011 10:49:30 +0100 [thread overview]
Message-ID: <87d3mv3pzp.fsf@gmx.de> (raw)
In-Reply-To: <b4m39nrxv9n.fsf@jpl.org> (Katsumi Yamaoka's message of "Mon, 14 Feb 2011 01:25:08 +0000")
Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> 2011-02-06 Michael Albinus <michael.albinus@gmx.de>
>
>> * auth-source.el (top): Require 'eieio unconditionally. Autoload
>> `secrets-get-attributes' instead of `secrets-get-attribute'.
>
> Gnus still supports Emacs 23.1 and earlier, however the eieio
> module is not available there. secrets.el is not, either.
> How do we manage the new auth-source.el?
For secrets.el, one could test availability of the package, and ignore
:secrets entries when it is not present.
For eieio.el it will be harder, because the new auth-source.el needs
defclass. Likely, we must provide eieio via the contrib directory.
Best regrads, Michael.
next prev parent reply other threads:[~2011-02-14 9:49 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 1:25 Katsumi Yamaoka
2011-02-14 1:45 ` Lars Ingebrigtsen
2011-02-14 15:33 ` Ted Zlatanov
2011-02-14 15:40 ` Richard Riley
2011-02-14 16:49 ` Ted Zlatanov
2011-02-14 17:39 ` David Engster
2011-02-14 18:02 ` Ted Zlatanov
2011-02-14 20:16 ` Lars Ingebrigtsen
2011-02-14 20:44 ` David Engster
2011-02-14 20:45 ` Reiner Steib
2011-02-14 21:09 ` Lars Ingebrigtsen
2011-02-14 22:01 ` Steinar Bang
2011-02-16 9:20 ` Reiner Steib
2011-02-16 19:10 ` Ted Zlatanov
2011-02-16 20:59 ` David Engster
2011-02-14 21:07 ` Ted Zlatanov
2011-02-14 21:18 ` Lars Ingebrigtsen
2011-02-14 21:26 ` David Engster
2011-02-14 21:39 ` Ted Zlatanov
2011-02-14 21:53 ` David Engster
2011-02-14 21:57 ` Lars Ingebrigtsen
2011-02-14 22:07 ` Ted Zlatanov
2011-02-14 22:20 ` Lars Ingebrigtsen
2011-02-14 22:33 ` Ted Zlatanov
2011-02-15 8:11 ` Reiner Steib
2011-02-15 8:41 ` David Engster
2011-02-15 13:43 ` Ted Zlatanov
2011-02-15 14:11 ` Steinar Bang
2011-02-16 20:28 ` Reiner Steib
2011-02-16 20:50 ` Ted Zlatanov
2011-02-16 22:16 ` Ted Zlatanov
2011-02-17 0:31 ` Katsumi Yamaoka
2011-02-17 0:40 ` Matt Lundin
2011-02-17 14:02 ` Steinar Bang
2011-02-17 17:06 ` Ted Zlatanov
2011-02-17 18:46 ` Steinar Bang
2011-02-17 22:01 ` Steinar Bang
2011-02-17 22:39 ` Lars Ingebrigtsen
2011-02-18 8:48 ` Steinar Bang
2011-02-18 10:52 ` Steinar Bang
2011-02-18 12:22 ` Steinar Bang
2011-02-18 20:26 ` Ted Zlatanov
2011-02-18 21:33 ` Charles Philip Chan
2011-02-19 18:00 ` Charles Philip Chan
2011-02-21 16:53 ` Charles Philip Chan
2011-02-18 22:11 ` Lars Ingebrigtsen
2011-02-22 21:53 ` Ted Zlatanov
2011-02-14 22:46 ` David Engster
2011-02-15 8:37 ` Steinar Bang
2011-02-14 22:18 ` David Engster
2011-02-14 22:04 ` Steinar Bang
2011-02-15 8:13 ` Jochen Hein
2011-02-16 20:15 ` Jochen Hein
2011-02-14 9:49 ` Michael Albinus [this message]
2011-02-14 15:26 ` Ted Zlatanov
2011-02-14 15:47 ` Michael Albinus
2011-02-14 16:54 ` Ted Zlatanov
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=87d3mv3pzp.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=ding@gnus.org \
--cc=yamaoka@jpl.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).