From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Installing binaries with package.el
Date: Thu, 09 Feb 2017 16:48:59 -0600 [thread overview]
Message-ID: <86k28zou90.fsf@stephe-leake.org> (raw)
In-Reply-To: <87zihvb0zr.fsf@Rainer.invalid> (Achim Gratz's message of "Thu, 09 Feb 2017 20:47:04 +0100")
Achim Gratz <Stromeko@nexgo.de> writes:
> Clément Pit-Claudel writes:
>> Sorry, maybe my original question wasn't clear. The question was: I
>> wrote a command line utility in ELisp (it doesn't provide interactive
>> commands; just a command line interface). What's the preferred way
>> for users to install it?
>
> I understood that to be the case, but it's a very surprising use of
> package.el and ELisp. As I said I don't really have a suggestion at the
> moment, but this particular use case should not be handled as an "Emacs
> package". You use Emacs as a VM for some scripting here.
I don't see any harm in this being an ELPA package.
>>> I simply don't think that wrapper scripts and/or compiling binaries
>>> is appropriate for ELPA packages, it just opens one big can of worms
>>> that I don't really want to deal with in any way.
>>
>> I don't understand this part too well. Are you saying that ELPA isn't
>> the right place to distribute a command line application written
>> entirely in ELisp? (Note that the task that I'm describing has
>> nothing to do with compiling binaries — sorry if that wasn't clear).
>
> Well, I would want to distinguish between Emacs packages proper and
> Emacs as a scripting VM. The more I think about it, package.el should
> guarantee that it doesn't write outside the package directory unless it
> has explicit user consent.
That's reasonable, but probably not enforceable. The
'post-install-action' run by package.el could be elisp code that firsts
asks permission, then runs a shell script to run the compiler.
--
-- Stephe
prev parent reply other threads:[~2017-02-09 22:48 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
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 [this message]
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=86k28zou90.fsf@stephe-leake.org \
--to=stephen_leake@stephe-leake.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.