unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Hackney <dan@haxney.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Sebastian Wiesner <lunaryorn@gmail.com>,
	Dmitry Gutov <dgutov@yandex.ru>,
	Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: cl-defstruct-based package.el, now with ert tests and no external tar!
Date: Tue, 25 Jun 2013 18:07:51 -0400	[thread overview]
Message-ID: <CAMqXDZvzZ7GckTDxxX+A65YMXwVXwT3ZPhCCeqZ3cQdUk-Ke2A@mail.gmail.com> (raw)
In-Reply-To: <jwvzjue9uim.fsf-monnier+emacs@gnu.org>

Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> Well, the list is long:
>
> Just to clarify: the reason why all this has changed without any
> discussion is because there was not supposed to be any API.
> `package.el' was only meant to provide an interactive UI, pretty much
> (plus a few functions, basically the autoloaded ones).

Part of the motivation for my changes was to give package.el more of
an API which would be usable by developers. There is certainly plenty
more which could be done, like having more of the refresh and
mark-upgradable functionality present in non-UI functions.

>>> What API?
>> Well, the package.el API, that is, "package-install",
>> "package-delete", "package-alist", and unfortunately a number of
>> internal functions ("package--*"), too, because the public API is
>> somewhat limited.

I separated things according to the principle of foo-public and
foo--private, so (theoretically) libraries using package.el should
only have to use package-foo functions and variables and none of
package--bar.

> Tell us what you need, then, and we can improve it.  As mentioned, what
> you think as the public API doesn't even really exist, so the design is
> very much open.

I intended to define a public API which would be solid enough to be
considered stable(ish).

>> Essentially, it's Bundler, but for Emacs Lisp.

I had thought about/proposed something along similar lines when
looking into version-parsing libraries [1], but was told that since
Emacs is not a production environment, it's not worth worrying too
much about exact version compatibility ranges (as in "package foo
depends on package bar >= 1.2.3 and < 1.3.0). Given that MELPA uses
simple date stamps from development versions, fine-grained control
over dependency graphs does not seem to be that important.

But who knows, maybe the presence of better version management will
enable more complex dependencies.

[1] http://www.haxney.org/2010/03/comparing-emacs-version-parsing.html

-- 
Daniel Hackney



  parent reply	other threads:[~2013-06-25 22:07 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-01 18:44 cl-defstruct-based package.el, now with ert tests and no external tar! Daniel Hackney
2013-04-04  1:55 ` Stefan Monnier
2013-04-05 16:32   ` Dmitry Gutov
2013-04-05 19:21     ` Stefan Monnier
2013-04-05 20:51     ` Daniel Hackney
2013-04-06 21:02       ` Ted Zlatanov
2013-04-07  0:43         ` Stefan Monnier
     [not found]           ` <jwv7gjt4arv.fsf-monnier+emacs@gnu.org>
2013-04-25  2:52             ` Daniel Hackney
2013-06-01 19:39               ` Dmitry Gutov
2013-06-04 21:25                 ` Daniel Hackney
2013-06-05 15:10                   ` Ted Zlatanov
2013-06-05 21:42                   ` Dmitry Gutov
2013-06-24 12:44                     ` Sebastian Wiesner
2013-06-25  1:19                       ` Stefan Monnier
2013-06-25 12:19                         ` Sebastian Wiesner
2013-06-25 13:58                           ` Stefan Monnier
2013-06-25 17:32                             ` Sebastian Wiesner
2013-06-25 18:23                               ` Stefan Monnier
2013-06-25 20:43                                 ` Sebastian Wiesner
2013-06-26  0:28                                   ` Stefan Monnier
2013-06-25 22:07                             ` Daniel Hackney [this message]
2013-06-26 23:04                           ` Nic Ferrier
     [not found]             ` <CAMqXDZtwnS-qUs8vCghYun0JZVuzofy4sCTMqdSskB2jJ9fq=g@mail.gmail.com>
     [not found]               ` <jwvobd3mg6l.fsf-monnier+emacs@gnu.org>
2013-06-12  2:18                 ` Stefan Monnier
2013-06-21  4:20                   ` Stefan Monnier
2013-06-21  7:49                     ` Dmitry Gutov
2013-06-21 14:56                       ` Stefan Monnier
2013-06-24 23:38                         ` Dmitry Gutov
2013-06-25 21:49                           ` Daniel Hackney
2013-06-26  7:35                             ` Dmitry Gutov
2013-06-27  9:38                             ` Dmitry Gutov

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=CAMqXDZvzZ7GckTDxxX+A65YMXwVXwT3ZPhCCeqZ3cQdUk-Ke2A@mail.gmail.com \
    --to=dan@haxney.org \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=lunaryorn@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    /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).