From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: auth-source.el and eieio
Date: Wed, 16 Feb 2011 21:28:43 +0100 [thread overview]
Message-ID: <87wrkzbu6c.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87d3mtmmzz.fsf@lifelogs.com> (Ted Zlatanov's message of "Tue, 15 Feb 2011 07:43:44 -0600")
On Tue, Feb 15 2011, Ted Zlatanov wrote:
> On Tue, 15 Feb 2011 Reiner Steib <reinersteib+gmane@imap.cc> wrote:
>>> On Mon, 14 Feb 2011 Lars Ingebrigtsen <larsi@gnus.org> wrote:
> LI> If this can be done cleanly (i.e., a lib directory that dgnushack.el
> LI> figures out whether to add to the load path (or not)), then I think
> LI> including it would be the way to go.
>
> RS> It is likely to lead to load-path shadows with weird effects.
> RS> [ Just imagine compiling Gnus from git on a system with several Emacs
> RS> versions (e.g. Debian-based systems). The user will probably compile
> RS> with the oldest Emacs and run the compiled version of Gnus with all
> RS> versions. With the newer Emacs, Gnus' EIEIO files will probably
> RS> shadow the newer ones from Emacs. ]
>
> We'll have to keep Gnus' EIEIO current. Since it hasn't changed much in
> 2 years I think it's not a big burden. We can actually start pulling
> all the EIEIO files from the Emacs Bazaar tree so we are in sync with
> the *Emacs* version of EIEIO.
That doesn't help when using release Gnus versions.
Here's a different idea: Wouldn't it be possible *not* to include the
EIEIO (or lib/) directory in load-path?
Then we'd load along these lines...
(ignore-errors
(or (require 'eieio))
;; lib/ from gnus/lisp/lib
(load "lib/eieio"))
(unless (featurep 'eieio)
(error "eieio not found in `load-path' or Gnus lib/ directory."))
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2011-02-16 20:28 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 [this message]
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
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=87wrkzbu6c.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.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).