From: phillip.lord@russet.org.uk (Phillip Lord)
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: windows installer
Date: Sat, 11 Nov 2017 11:34:08 +0000 [thread overview]
Message-ID: <87fu9l3v7z.fsf@russet.org.uk> (raw)
In-Reply-To: <83h8u1p8vt.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 11 Nov 2017 09:33:26 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Stefan Monnier <monnier@iro.umontreal.ca>
>> Date: Fri, 10 Nov 2017 15:46:09 -0500
>>
>> > They _will_ want to add it to PATH if they want to install packages
>> > from the likes of ELPA, which frequently come with Makefiles that
>> > invoke Emacs to compile the Lisp files.
>>
>> For lack of familiarity with the Windows world, I don't know if typical
>> Windows users will want to add it to PATH (as a GNU/Linux user, of
>> course I'd do that), but I think the "frequently" above is incorrect.
>>
>> The way Elisp files are compiled by package.el is to do it in the
>> running Emacs rather than by executing a separate Emacs session, AFAIK.
>>
>> And even if you configure it to use something like async.el, doesn't
>> (expand-file-name invocation-name invocation-directory) let async.el find
>> an Emacs executable even when it's not in PATH?
>
> Maybe I'm missing something. 29 packages (out of 166) in ELPA have a
> Makefile. Taking just one random Makefile, company/Makefile, I see
> this:
>
> EMACS=emacs
> [...]
>
> compile:
> ${EMACS} -Q --batch -L . -f batch-byte-compile company.el company-*.el
>
> If this Makefile is invoked with "make compile", it clearly expects
> Emacs to be found along PATH. And even if Make is invoked from Emacs,
> the directory where the Emacs binary was found is not added to PATH.
> So how can this work without Emacs's binary being on PATH? And what
> am I missing here?
This is just not a function of ELPA, it's a function of the ELPA source.
Phil
next prev parent reply other threads:[~2017-11-11 11:34 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 23:11 windows installer Phillip Lord
2017-10-28 21:47 ` Richard Stallman
2017-11-06 8:11 ` Jostein Kjønigsen
[not found] ` <87h8u6bae3.fsf@russet.org.uk>
[not found] ` <WM!524810e63610127669556b68fb62cde560daf19be50fc52d4d63dd232af7bdb0490810e03b84a6559c9b2017d8462cc3!@mailhub-mx4.ncl.ac.uk>
2017-11-08 7:31 ` Jostein Kjønigsen
2017-11-10 17:01 ` Phillip Lord
2017-11-10 18:52 ` Eli Zaretskii
2017-11-10 20:46 ` Stefan Monnier
2017-11-10 21:22 ` John Mastro
2017-11-10 21:35 ` Fabrice Popineau
2017-11-11 7:33 ` Eli Zaretskii
2017-11-11 11:34 ` Phillip Lord [this message]
2017-11-11 14:57 ` Stefan Monnier
2017-11-12 11:21 ` Jostein Kjønigsen
2017-11-10 21:33 ` Fabrice Popineau
2017-11-11 7:35 ` Eli Zaretskii
2017-11-10 23:27 ` Phillip Lord
2017-11-11 0:25 ` Fabrice Popineau
2017-11-11 11:25 ` Phillip Lord
2017-11-12 0:30 ` Fabrice Popineau
2017-11-12 4:30 ` Eli Zaretskii
[not found] ` <87fu9hbytq.fsf@russet.org.uk>
2017-11-13 22:25 ` Phillip Lord
2017-11-14 13:08 ` Fabrice Popineau
2017-11-16 16:15 ` Phillip Lord
2017-11-11 7:48 ` Eli Zaretskii
2017-11-11 11:24 ` Phillip Lord
2017-11-11 12:01 ` Eli Zaretskii
[not found] ` <<83ineiotjr.fsf@gnu.org>
2017-11-10 21:43 ` Drew Adams
2017-11-10 23:35 ` Phillip Lord
2017-11-11 7:49 ` Eli Zaretskii
2017-11-11 7:40 ` Eli Zaretskii
2017-11-11 9:42 ` Yuri Khan
2017-11-11 10:37 ` Eli Zaretskii
2017-11-11 16:39 ` Drew Adams
[not found] ` <87a7zpbxza.fsf@russet.org.uk>
2017-11-13 22:44 ` Phillip Lord
2017-11-14 14:54 ` Drew Adams
2017-11-16 16:15 ` Phillip Lord
2017-11-16 16:23 ` Eli Zaretskii
2017-11-16 16:31 ` Fabrice Popineau
2017-11-16 16:57 ` Eli Zaretskii
2017-11-16 17:35 ` Fabrice Popineau
2017-11-16 17:39 ` Eli Zaretskii
2017-11-16 18:10 ` Fabrice Popineau
2017-11-16 20:45 ` Richard Copley
2017-11-17 7:14 ` Eli Zaretskii
2017-11-17 7:22 ` Fabrice Popineau
2017-11-17 7:35 ` Eli Zaretskii
2017-11-17 7:25 ` Fabrice Popineau
2017-11-16 17:42 ` Noam Postavsky
2017-11-16 17:45 ` Fabrice Popineau
2017-11-22 22:39 ` Phillip Lord
-- strict thread matches above, loose matches on Subject: below --
2017-11-12 8:56 Angelo Graziosi
2017-11-12 9:03 ` Fabrice Popineau
2017-11-12 11:30 ` Eli Zaretskii
2017-11-12 12:39 ` Fabrice Popineau
[not found] ` <8760adbxw6.fsf@russet.org.uk>
2017-11-13 22:46 ` Phillip Lord
2017-11-14 14:36 ` Angelo Graziosi
2017-11-14 16:31 ` Fabrice Popineau
2017-11-14 20:12 ` Angelo Graziosi
2017-11-20 8:46 ` Jostein Kjønigsen
2017-11-20 18:07 ` Eli Zaretskii
2017-11-22 23:01 ` Phillip Lord
2017-11-23 3:43 ` Eli Zaretskii
2017-11-23 18:06 ` Phillip Lord
2017-11-23 20:09 ` Eli Zaretskii
2017-11-24 19:13 ` Phillip Lord
2017-11-24 19:56 ` Eli Zaretskii
2017-11-25 11:08 ` Phillip Lord
2017-11-25 12:56 ` Eli Zaretskii
2017-11-27 17:56 ` Phillip Lord
2017-11-12 14:14 ` Angelo Graziosi
2017-11-12 11:28 ` Eli Zaretskii
2017-11-12 14:27 ` Angelo Graziosi
2017-11-12 15:04 ` Eli Zaretskii
2017-11-12 17:32 ` Angelo Graziosi
2017-11-12 18:42 ` Eli Zaretskii
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=87fu9l3v7z.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--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).