unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Installing binaries with package.el
Date: Tue, 7 Feb 2017 08:12:21 -0500	[thread overview]
Message-ID: <76433d89-f381-b805-4501-c9c8b8f7a275@gmail.com> (raw)
In-Reply-To: <871svatqh0.fsf@mbork.pl>

On 2017-02-07 02:22, Marcin Borkowski wrote:
> I have no idea, frankly speaking.  AFAIK, pdf-tools does use /some/
> binary, and is installed via package-install (and AFAIR, I didn't have
> to add anything to the $PATH variable) - so there must be some way it
> does it, and that's practically all I know.  (One more thing, I don't
> know whether it's significant, but I have to reinstall it every time
> I compile a new Emacs.  No idea why exactly.)

I see, thanks.  AFAICT, pdf-tools does not install a systel-level binary; it just compiles a C program as part of its installation procedure, and then calls it — but it does not try to expose that binary to the user.  This means among other things that it doesn't need to create files outside of its installation folder, for example.

My case is a bit different.  The binary is just a bash wrapper around an Emacs Lisp program, so I don't have compilation-related issues; I do, however, want my users to be able to call the program easily, which probably means that I want to create binaries outside of my package's installation folder (which in turns has consequences on uninstallation behaviour: deleting the installation folder isn't enough).

Cheers,
Clément.




  reply	other threads:[~2017-02-07 13:12 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 [this message]
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

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=76433d89-f381-b805-4501-c9c8b8f7a275@gmail.com \
    --to=cpitclaudel@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=mbork@mbork.pl \
    /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).