From: Stefan Monnier <monnier@iro.umontreal.ca>
To: raman@google.com (T.V Raman)
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>, emacs-devel@gnu.org
Subject: Re: Info Pages for ELPA packages
Date: Tue, 27 May 2014 15:49:00 -0400 [thread overview]
Message-ID: <jwvy4xnoviy.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <p91vbsrmejh.fsf@lapdog.roam.corp.google.com> (T. V. Raman's message of "Tue, 27 May 2014 08:23:14 -0700")
> is perhaps the directory layout of elpa installations -- 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
The directory layout expected from elpa packages is "everything at
top-level". Which works great for simple packages.
> One simple first step might be to say that .el files of package foo
> should go into elpa/foo/lisp -- and then mandate that foo should also
> have subdirs texi and info -- for texinfo sources and built info pages
> respectively. This will also open up space for then mandating foo/etc
> foo/src etc over time.
There are too many options, so the way forward is not to impose
a structure, nor to try and provide support for the various structures
that make sense (because that would be too unwieldy). Instead,
package.el should do less, letting the package do the work whichever way
it likes, instead.
Stefan
next prev parent reply other threads:[~2014-05-27 19:49 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
2014-05-27 19:49 ` Stefan Monnier [this message]
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=jwvy4xnoviy.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
--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).