unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mario Lang <mlang@delysid.org>
To: emacs-devel@gnu.org
Subject: Re: [elpa] chess.el: Req. for comment/review: Info manual
Date: Wed, 18 Jun 2014 21:20:34 +0200	[thread overview]
Message-ID: <87iony6n3x.fsf@fx.delysid.org> (raw)
In-Reply-To: <jwvegym3v15.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 18 Jun 2014 14:58:53 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> Why did I need to read the Lisp source to figure out how to checkout
>> a single package from externals?
>
> I wouldn't know.  I made it as simple as I could, because I don't have
> much time to devote to it and nobody else seemed interested in spending
> time on it, whereas I think GNU ELPA is very important for Emacs.

I am actually rather motivated to work on ELPA, but I am too green to do
any infrastructure changes just yet.

THat said, what might be confusing is the "externals/" prefix, since it
suggests that the package is really externally maintained.  As it
stands, we seem to use separate branches for packages to keep history
apart, which is a valid enough reason with big packages methinks.  We
*could* clear up that confusion by using another branch prefix, like
"packages/" to indicate that these are really packages native to the ELPA repo.

I also find the instructions to generate archives locally which include
externals a bit too verbose.  I'd rather prefer to have a make target
that does all the work, so that it becomes more easy to test-build a
package living in a separate branch locally.

-- 
CYa,
  ⡍⠁⠗⠊⠕



  parent reply	other threads:[~2014-06-18 19:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-12 19:23 [elpa] chess.el: Req. for comment/review: Info manual Mario Lang
2014-06-14 16:48 ` Eli Zaretskii
2014-06-14 18:48   ` Mario Lang
2014-06-14 19:08   ` Mario Lang
2014-06-14 19:24     ` Eli Zaretskii
2014-06-14 21:09       ` Stefan Monnier
2014-06-18 15:09 ` Eli Zaretskii
2014-06-18 18:09   ` Stefan Monnier
2014-06-18 18:34     ` Eli Zaretskii
2014-06-18 18:55       ` Stefan Monnier
2014-06-18 19:11         ` Eli Zaretskii
2014-06-18 20:29           ` Stefan Monnier
2014-06-19  2:42             ` Eli Zaretskii
2014-06-18 18:20   ` Mario Lang
2014-06-18 18:36     ` Eli Zaretskii
2014-06-18 18:58       ` Stefan Monnier
2014-06-18 19:13         ` Eli Zaretskii
2014-06-18 20:36           ` Stefan Monnier
2014-06-19  2:44             ` Eli Zaretskii
2014-06-19 15:18               ` Richard Stallman
2014-06-19 15:22                 ` Eli Zaretskii
2014-06-18 19:20         ` Mario Lang [this message]
2014-06-18 20:36           ` Stefan Monnier
2014-06-19  3:37       ` Glenn Morris
2014-06-19 15:18     ` Eli Zaretskii

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=87iony6n3x.fsf@fx.delysid.org \
    --to=mlang@delysid.org \
    --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).