all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: emacs-pdf-tools: Add missing input.
Date: Tue, 15 Mar 2016 15:27:16 +0100	[thread overview]
Message-ID: <87d1qvrf3v.fsf@gnu.org> (raw)
In-Reply-To: <87vb4tnyxe.fsf@gmail.com> (Alex Kost's message of "Fri, 11 Mar 2016 12:31:25 +0300")

Alex Kost <alezost@gmail.com> skribis:

> The bottom line of the following text is the question: Is it possible to
> combine 2 (or more) build systems for building a package?

Sure!

> I did a little experiment: I thought maybe it could be possible just to
> pick some build phases from (guix build emacs-build-system), so I added
> this module to #:modules and #:imported-modules and added phases like
> this:
>
>   (modify-phases %standard-phases
>     ;; ...
>     (add-after 'build 'emacs-build
>       (@@ (guix build emacs-build-system) build))
>     (add-after 'install 'emacs-install
>       (@@ (guix build emacs-build-system) install)))
>
> The package was built successfully, but the result was not good, because
> both gnu-build-system and emacs-build-system import %standard-phases :-)

You mean “export”?

I think you can always add a renamer upon import, using something like:

  (package
    ;; …
    (arguments
     `(#:imported-modules ((guix build emacs-build-system)
                           ,%gnu-build-system-modules)
       #:modules (((guix build emacs-build-system) #:prefix emacs:)
                  ,%gnu-build-system-modules)

       #:phases (modify-phases %standard-phases   ;from gnu-build-system
                  (add-before 'build 'emacs-build
                     (assoc-ref emacs:%standard-phases 'build))
                  ;; …
                  ))))

Would it work for you?

> From 5692ba83371fea16a34ff20d1f5d743f05173348 Mon Sep 17 00:00:00 2001
> From: Alex Kost <alezost@gmail.com>
> Date: Fri, 11 Mar 2016 11:34:20 +0300
> Subject: [PATCH] gnu: emacs-pdf-tools: Add missing input.
>
> This is a followup to commit eccd0b57a1f05b3caca28604f4d2c06556e2fe05.
>
> * gnu/packages/emacs.scm (emacs-pdf-tools)[propagated-inputs]: Add
> 'let-alist'.
> [arguments]: Adjust 'install-lisp' phase to compile pdf-tools using
> let-alist library.

Otherwise the patch LGTM.

Ludo’.

  reply	other threads:[~2016-03-15 14:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11  9:31 [PATCH] gnu: emacs-pdf-tools: Add missing input Alex Kost
2016-03-15 14:27 ` Ludovic Courtès [this message]
2016-03-15 20:15   ` Alex Kost
2016-03-15 21:40     ` Ludovic Courtès

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=87d1qvrf3v.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=alezost@gmail.com \
    --cc=guix-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/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.