From: Alex Kost <alezost@gmail.com>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Which Emacs version used to build Emacs packages with emacs-checkout?
Date: Fri, 08 Sep 2017 23:31:51 +0300 [thread overview]
Message-ID: <87h8wdc4p4.fsf@gmail.com> (raw)
In-Reply-To: <877exa5oph.fsf@gmail.com> (Oleg Pykhalov's message of "Thu, 07 Sep 2017 21:49:14 +0300")
Oleg Pykhalov (2017-09-07 21:49 +0300) wrote:
> Hello Guix,
>
> Here is a =emacs-checkout= snippet which works for me. Enjoy it if
> somebody need it.
>
> I'm little bit confused about Emacs **version** that is used inside
> =emacs-build-systems= and inputs which use =emacs-minimal=.
>
> If I define a new package with =-checkout= suffix and install it, for
> example =guix package -i emacs@26.0.50-1.f0eb70d= it works fine.
>
> As I notice all packages which uses =emacs-build-system= will use
> original Guix Emacs version package. Am I right?
Right, by default 'emacs-build-system' uses the current 'emacs-minimal'
package.
> Then, all Emacs packages will be build by =emacs-minimal= which is
> original Guix Emacs version.
Yes. Note that this default emacs can be overrided on a package level
by using #:emacs keyword in the arguments. See 'emacs-auctex' package
for example.
> I found =(setq load-prefer-newer t)= way to avoid loading old compiled
> elisp files, but it's not what I really want.
This (I mean 'load-prefer-newer') is one of my favourite setting :-)
But it is not clear for me, what do you really want?
> Thoughts? :-)
Sorry, but I don't understand what you are asking about :-)
--
Alex
next prev parent reply other threads:[~2017-09-08 20:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 18:49 Which Emacs version used to build Emacs packages with emacs-checkout? Oleg Pykhalov
2017-09-08 20:31 ` Alex Kost [this message]
2017-09-22 13:49 ` Oleg Pykhalov
2017-09-29 10:57 ` Alex Kost
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h8wdc4p4.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=go.wigust@gmail.com \
--cc=help-guix@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.
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).