Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Gnus installation
Date: Sat, 01 Oct 2005 12:46:39 +0200	[thread overview]
Message-ID: <ilu3bnlh5v4.fsf@latte.josefsson.org> (raw)
In-Reply-To: <b4m1x36wvn4.fsf@jpl.org> (Katsumi Yamaoka's message of "Fri, 30 Sep 2005 22:08:31 +0900")

Katsumi Yamaoka <yamaoka@jpl.org> writes:

>>>>>> In <ilu4q82iy2o.fsf@latte.josefsson.org> Simon Josefsson wrote:
>
>> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>
>>> When installing Gnus, specifying no options, a lot of Lisp files
>>> will be scattered underneath the site-lisp directory.  I considered
>>> over ten years that it's not a good idea.
>
>> FWIW, I like this.  Emacs do search for files beneath site-lisp by
>> default, right?
>
> Yes, indeed.  Especially in the Emacs 18 era, people might not
> have preferred to use subdirectories since they had to be added
> to load-path manually, though we have now subdirs.el which adds
> subdirectories to load-path automatically.  The reason I don't
> like it is because I have many files underneath the site-lisp
> directory.  So, I always use `--with-lispdir=site-lisp/gnus'.
> There's also another usefulness in this; I only do `rm -fr gnus'
> when I need to remove old Gnus files, for example.  Furthermore,
> the Emacs version of Gnus is installed in the gnus subdirectory.

Ok.  You have my vote.

>>> In addition to this,
>>> there's another problem that ``./configure; make install'' will
>>> never install .el files.  WDYT?
>
> It won't be a matter, if people always use ``make; make install''.
> However, those who fully trust Gnus might do that, and they will
> not be able to get meaningful backtrace when they are betrayed.

And further, *.el contain online documentation, so they really should
be installed IMHO.



  reply	other threads:[~2005-10-01 10:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-30  1:20 Katsumi Yamaoka
2005-09-30 11:39 ` Simon Josefsson
2005-09-30 13:08   ` Katsumi Yamaoka
2005-10-01 10:46     ` Simon Josefsson [this message]
2005-10-02 23:41       ` Katsumi Yamaoka
2005-10-03  0:31         ` NAKAJI Hiroyuki
2005-10-03  0:44           ` Katsumi Yamaoka
2005-10-04  9:39             ` Katsumi Yamaoka
2005-10-03  6:59         ` Adam Sjøgren
2005-10-03 11:13           ` Reiner Steib
2005-10-03  8:40         ` Simon Josefsson
     [not found]         ` <b4mbr27wkoo.fsf-NvgVpDro27E@public.gmane.org>
2005-10-03  8:40           ` Jochen Küpper
2005-10-03 16:58         ` Wes Hardaker
2005-10-03 16:59         ` Wes Hardaker

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=ilu3bnlh5v4.fsf@latte.josefsson.org \
    --to=jas@extundo.com \
    --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).