From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: emacs-devel@gnu.org
Subject: GNU ELPA structure
Date: Sun, 29 Apr 2012 11:20:11 -0400 [thread overview]
Message-ID: <jwvipgiwoyx.fsf-monnier+emacs@gnu.org> (raw)
Currently, GNU ELPA contains sufficiently few packages, that a flat list
is OK, but will soon become inconvenient for end-users.
So we should start thinking about how to structure the space of
ELPA packages. I think a first division is between packages that only
provide functions for use by other packages (which I'd call "libraries")
and "end-user packages" which provide commands the user can use directly.
After that we could either have a tree structure (somewhat like the
subdirs in `emacs/lisp'), or otherwise rely on "tags", which would
probably be taken from the "keywords:" package header.
Stefan
reply other threads:[~2012-04-29 15:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=jwvipgiwoyx.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.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.
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).