From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: raman@google.com (T.V Raman)
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: Info Pages for ELPA packages
Date: Wed, 28 May 2014 01:03:13 +0900 [thread overview]
Message-ID: <87ha4b8b0e.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <p91vbsrmejh.fsf@lapdog.roam.corp.google.com>
T.V Raman writes:
> there seems to be place for nothing but the elisp files at first
> glance ie each package has to maintain a subdirectory structure of
> its own
I hope you guys can find a good solution, but what XEmacs discovered
in trying to handle this problem in its package system is that there
are just too many ways of doing it in the real packages out there, and
we ended up with a horrible set of make variables to point the package
system to where various items live in the source tree for a package
(various data files are even worse, I think we have about 26
DATA_DIR_## make variables).
On the other hand, the system does work even if the internals are
klunky, and the installed tree is very regular. (David K, don't
bother pointing out that it's suboptimal, I'm not suggesting that ELPA
emulate the XEmacs package system!)
next prev parent reply other threads:[~2014-05-27 16:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-25 0:01 Info Pages for ELPA packages T. V. Raman
2014-05-25 1:41 ` Glenn Morris
2014-05-25 22:05 ` Mario Lang
2014-05-26 4:37 ` raman
2014-05-26 17:54 ` Stefan Monnier
2014-05-26 22:38 ` T.V Raman
2014-05-27 2:40 ` Eric Abrahamsen
2014-05-27 2:47 ` raman
2014-05-27 3:25 ` Stefan Monnier
2014-05-27 15:23 ` T.V Raman
2014-05-27 16:03 ` Stephen J. Turnbull [this message]
2014-05-27 19:49 ` Stefan Monnier
2014-05-27 3:26 ` Stefan Monnier
2014-05-27 4:43 ` Eric Abrahamsen
2014-05-27 10:06 ` Mario Lang
2014-05-27 11:50 ` Michael Albinus
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ha4b8b0e.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=monnier@iro.umontreal.ca \
--cc=raman@google.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).