all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: How to install prerelease package versions (particularly Emacs)
Date: Thu, 12 Apr 2018 22:27:34 -0700	[thread overview]
Message-ID: <871sfjzneh.fsf@gmail.com> (raw)
In-Reply-To: <873700pz45.fsf@gmail.com> (Pierre Neidhardt's message of "Thu, 12 Apr 2018 14:42:26 +0530")


[-- Attachment #1.1: Type: text/plain, Size: 3187 bytes --]

Hi Pierre,

Pierre Neidhardt <ambrevar@gmail.com> writes:

> Chris Marusich <cmmarusich@gmail.com> writes:
>
>> Can you share the package definition?
>
> Let's start from the most straight-forward:
>
> (define-public emacs-dev
>   (package
>    (inherit emacs)
>    (name "emacs-dev")
>    (version "26.0.91")
>    (source
>      (local-file "/home/ambrevar/projects/emacs-build" #:recursive? #t))))

I took this definition and adapted it as shown in the attached file.  I
then did the following things:

* Save the file at /tmp/emacs.scm.

* Clone Emacs' Git repository into /tmp/emacs at commit
  93678bffe6427b9d83dae032c56a4e480539a4a7.

* Get an environment with the necessary dependencies, and run autogen.sh:

    guix environment emacs

  You could try with --pure to see if the emacs inputs are actually
  enough to bootstrap Emacs' Git repository.  I doubt they are.  You can
  experiment with adding dependencies by using the --ad-hoc option.
  Once you figure out what dependencies are required to run autogen.sh,
  you can add them to your custom package definition if you want
  (although they won't be required for building Emacs once you've built
  the "configure" script).

  I happen to have various tools, such as Autoconf, installed in my
  profile (mainly so I can browse the manuals locally).  I'm pretty sure
  that's why the next step succeeded for me.

* Run autogen.sh to create the "configure" script:

    ./autogen.sh

* Now that the "configure" script has been created, build Emacs:

    guix build -f /tmp/emacs.scm

For me, the build proceeded but then failed during the "check" phase:

--8<---------------cut here---------------start------------->8---
SUMMARY OF TEST RESULTS
-----------------------
Files examined: 195
Ran 2767 tests, 2619 results as expected, 24 unexpected, 124 skipped
7 files contained unexpected results:
  src/process-tests.log
  lisp/progmodes/xref-tests.log
  lisp/progmodes/flymake-tests.log
  lisp/files-tests.log
  lisp/eshell/em-ls-tests.log
  lisp/calendar/todo-mode-tests.log
  lisp/net/tramp-tests.log
make[2]: *** [Makefile:280: check-doit] Error 1
make[2]: Leaving directory '/tmp/guix-build-emacs-dev-26.0.91.drv-0/build/test'
make[1]: *** [Makefile:255: check] Error 2
make[1]: Leaving directory '/tmp/guix-build-emacs-dev-26.0.91.drv-0/build/test'
make: *** [Makefile:945: check] Error 2
phase `check' failed after 104.0 seconds
builder for `/gnu/store/dshw12bj2486lcfv65g04g9rznxgfrwp-emacs-dev-26.0.91.drv' failed with exit code 1
@ build-failed /gnu/store/dshw12bj2486lcfv65g04g9rznxgfrwp-emacs-dev-26.0.91.drv - 1 builder for `/gnu/store/dshw12bj2486lcfv65g04g9rznxgfrwp-emacs-dev-26.0.91.drv' failed with exit code 1
guix build: error: build failed: build of `/gnu/store/dshw12bj2486lcfv65g04g9rznxgfrwp-emacs-dev-26.0.91.drv' failed
--8<---------------cut here---------------end--------------->8---

I don't know much about the test failures, but this is a success as far
as I'm concerned: If you get this far, it means the local-file
declaration in your package definition is working as intended.

Hope that helps!

-- 
Chris

[-- Attachment #1.2: emacs.scm --]
[-- Type: application/octet-stream, Size: 194 bytes --]

(use-modules
 (guix packages)
 (guix gexp)
 (gnu packages emacs))

(package
  (inherit emacs)
  (name "emacs-dev")
  (version "26.0.91")
  (source
   (local-file "/tmp/emacs" #:recursive? #t)))

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  parent reply	other threads:[~2018-04-13  5:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-03  0:00 How to install prerelease package versions (particularly Emacs) Jorge
2018-03-03 10:24 ` Oleg Pykhalov
2018-03-19  4:13   ` Chris Marusich
2018-03-26 18:42     ` Pierre Neidhardt
2018-03-27  9:51       ` Ludovic Courtès
2018-03-27 12:24         ` Clément Lassieur
2018-03-27 15:33         ` Oleg Pykhalov
2018-03-27 17:46           ` Marius Bakke
2018-03-27 20:57           ` Ludovic Courtès
2018-03-28  7:12             ` Oleg Pykhalov
2018-03-30  7:06               ` Pierre Neidhardt
2018-03-30 12:13                 ` Mathieu Lirzin
2018-03-30 12:19                   ` Pierre Neidhardt
2018-03-30 13:08                     ` Mathieu Lirzin
2018-04-11 15:53                       ` Pierre Neidhardt
2018-04-12  8:29                         ` Chris Marusich
2018-04-12  9:12                           ` Pierre Neidhardt
2018-04-12 12:57                             ` Ricardo Wurmus
2018-04-12 13:21                               ` Pierre Neidhardt
2018-04-13  5:27                             ` Chris Marusich [this message]
2018-04-13  5:57                         ` Carlo Zancanaro
2018-04-01 14:09                 ` Oleg Pykhalov
2018-04-11 16:00                   ` Pierre Neidhardt
2018-04-12  8:28                     ` Chris Marusich
2018-04-12  8:32                       ` Pierre Neidhardt
2018-04-11 15:57               ` Pierre Neidhardt
2018-04-12  6:06                 ` Pierre Neidhardt
2018-04-05 15:53       ` Jorge
2018-04-05 19:36         ` Pierre Neidhardt
2018-03-03 13:46 ` Jorge

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=871sfjzneh.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=ambrevar@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.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.