all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Proposals for fixing package-initialize
Date: Mon, 04 Sep 2017 18:28:56 +0200	[thread overview]
Message-ID: <873782whpz.fsf@zigzag> (raw)
In-Reply-To: <CADB4rJH_GkduJALjCkQAqHuvP5om561hihzcao+9RL+iMHAJ7Q@mail.gmail.com> (Radon Rosborough's message of "Sun, 3 Sep 2017 22:31:57 -0700")

[-- Attachment #1: Type: text/plain, Size: 2205 bytes --]


() Radon Rosborough <radon.neon@gmail.com>
() Sun, 3 Sep 2017 22:31:57 -0700

   This email is an attempt to present all the proposals that
   have been discussed, in an even-handed way, so that we can
   make a decision without everyone needing to have read the
   aforementioned 150 emails.

Cool, thanks!  I now feel less guilty skimming through that
backlog.  I appreciate the clear presentation style, too.

   ==> Proposal F: Use more declarative configuration

   Summary:
     - make it so that packages can be configured in a way that
       causes package-initialize to be called automatically

   Advantages:
     - would solve all the problems

   Disadvantages:
     - nobody has any idea how to do this
     - and it would probably take several years anyway

This strikes me as the best long-term fix (i.e., defining a data
format, thus giving space to various package manglers to bloom,
wither and die around it, improving it as time goes on).

It's hyperbole to say nobody has any idea, however -- there are
several general text-oriented serialization formats that people
have already defined (e.g., YAML, JSON, sexps).  Any of these
can be easily adapted to the package-metadata domain.  Re time,
granted, settling on a suitable filename extension might take
years (i'll throw out ".epdef" for "Emacs package definition"),
but i think a few weeks (months) of nailing down .epdef by one
person (serial) would inspire very rapid (re-)development of
programs afterwards (parallel) resulting in overall wall-time of
much less than several years.

Sez Perlis:

 We kid ourselves if we think that the ratio of procedure to
 data in an active data-base system can be made arbitrarily
 small or even kept small.

so the trick for Someone will be to define ONLY a data format,
and refrain from stepping into "an active data-base system" (as
much as possible -- w/ Emacs, there be hooks a-lurking 'neath).

-- 
Thien-Thi Nguyen -----------------------------------------------
 (defun responsep (query)
   (pcase (context query)
     (`(technical ,ml) (correctp ml))
     ...))                              748E A0E8 1CB8 A748 9BFA
--------------------------------------- 6CE4 6703 2224 4C80 7502


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2017-09-04 16:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-04  5:31 Proposals for fixing package-initialize Radon Rosborough
2017-09-04 12:47 ` Drew Adams
2017-09-04 16:28 ` Thien-Thi Nguyen [this message]
2017-09-04 16:36   ` Radon Rosborough
2017-09-05 16:41 ` Howard Melman
2017-09-07 15:55 ` Clément Pit-Claudel
2017-09-14 19:55 ` Ted Zlatanov
2017-09-15  1:30   ` Radon Rosborough
2017-09-15 12:35     ` Stefan Monnier

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=873782whpz.fsf@zigzag \
    --to=ttn@gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.