unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: Installing binaries with package.el
Date: Thu, 09 Feb 2017 11:20:41 -0500	[thread overview]
Message-ID: <87a89vmj3a.fsf@flea> (raw)
In-Reply-To: jwvd1er34db.fsf-monnier+emacs@gnu.org

On Thu, 09 Feb 2017 08:10:58 -0500 Stefan Monnier <monnier@iro.umontreal.ca> wrote: 

>> Do you think OS distributions will pick up the module distribution
>> piece like they did with Python, Perl, etc.?

SM> Not sure what you mean.  Debian does already provide various ELPA
SM> packages, so I guess the answer is yes, but I don't think this will be
SM> of much help to the above problems (it just lets the user choose whether
SM> to install a package via ELP or via dpkg, and only for those packages
SM> which Debian has packaged as a dpkg).  IOW, they do a parallel job,
SM> which doesn't really help us (not to imply that it hurts, tho).

If Debian will keep track of package dependencies, and we are not so
worried about other platforms (expecting them to match Debian's
approach), and we're satisfied that their approach resolves the issues
I've brought up (OS package dependencies and dynload module/general
binary distribution), then it's a lot less important to have
dependencies on OS packages in ELPA packages or to provide any binaries
(the two ELPA features I've proposed so far).

If we agree on that, then ELPA packages of dynload modules only have to
support local compilation for developers.

Ted




  reply	other threads:[~2017-02-09 16:20 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-07  2:09 Installing binaries with package.el Clément Pit--Claudel
2017-02-07  5:29 ` Marcin Borkowski
2017-02-07  5:33   ` Clément Pit-Claudel
2017-02-07  7:22     ` Marcin Borkowski
2017-02-07 13:12       ` Clément Pit-Claudel
2017-02-07 15:07         ` Ted Zlatanov
2017-02-07 16:15           ` Clément Pit-Claudel
2017-02-07 19:40             ` Ted Zlatanov
2017-02-09 13:10               ` Stefan Monnier
2017-02-09 16:20                 ` Ted Zlatanov [this message]
2017-02-09 17:39                   ` Stefan Monnier
2017-02-09 19:36                     ` Ted Zlatanov
2017-02-09 22:43                     ` Stephen Leake
2017-02-08 18:40     ` Andreas Politz
2017-02-09 15:33       ` Stefan Monnier
2017-02-09 21:55         ` Andreas Politz
2017-02-10  6:09           ` Stefan Monnier
2017-02-07 16:05 ` Stefan Monnier
2017-02-07 16:16   ` Clément Pit-Claudel
2017-02-07 16:58     ` Aurélien Aptel
2017-02-07 17:45       ` Stefan Monnier
2017-02-07 20:17 ` Achim Gratz
2017-02-07 21:58   ` Clément Pit-Claudel
2017-02-07 23:34     ` Kaushal Modi
2017-02-08  1:35       ` Clément Pit-Claudel
2017-02-08 18:52     ` Achim Gratz
2017-02-08 19:17       ` Andreas Politz
2017-02-08 19:44         ` Achim Gratz
2017-02-08 21:36       ` Clément Pit-Claudel
2017-02-09 19:47         ` Achim Gratz
2017-02-09 20:11           ` Clément Pit-Claudel
2017-02-09 22:48           ` Stephen Leake

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=87a89vmj3a.fsf@flea \
    --to=tzz@lifelogs.com \
    --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).