[PATCH 2/6] build-system/emacs: Use "emacs" from native-inputs if specified.

[PATCH 2/6] build-system/emacs: Use "emacs" from native-inputs if specified.

[Federico Beffa]

Alex Kost <alezost@gmail.com> writes:

> * guix/build-system/emacs.scm (lower): Do not add "emacs" to
>   build-inputs if it is already specified in the native-inputs.
> @@ -73,8 +75,16 @@
>
>                          ;; Keep the standard inputs of 'gnu-build-system'.
>                          ,@(standard-packages)))
> -         (build-inputs `(("emacs" ,emacs)
> -                         ,@native-inputs))
> +         ;; Add emacs to build-inputs only if native-inputs do not contain
> +         ;; emacs already.  This allows us to use non-default emacs for
> +         ;; building.
> +         (build-inputs (if (find (match-lambda
> +                                   (("emacs" _ ...) #t)
> +                                   (_ #f))
> +                                 native-inputs)
> +                           native-inputs
> +                           `(("emacs" ,emacs)
> +                             ,@native-inputs)))

Note that for the interpreter we normally use a keyword, here #:emacs
(in a similar way as, say, for the python-build-system there is
#:python).  Your code overwrites its effect in a non-transparent way.

Please use the keyword in the packages where you need an emacs package
different from the default one, or remove all the code related to the
keyword.  If you opt for the second one, please be consistent and do the
same for all other build systems.

Fede

Re: [PATCH 2/6] build-system/emacs: Use "emacs" from native-inputs if specified.

[Ludovic Courtès]

Federico Beffa <beffa@ieee.org> skribis:

> Alex Kost <alezost@gmail.com> writes:
>
>> * guix/build-system/emacs.scm (lower): Do not add "emacs" to
>>   build-inputs if it is already specified in the native-inputs.
>> @@ -73,8 +75,16 @@
>>
>>                          ;; Keep the standard inputs of 'gnu-build-system'.
>>                          ,@(standard-packages)))
>> -         (build-inputs `(("emacs" ,emacs)
>> -                         ,@native-inputs))
>> +         ;; Add emacs to build-inputs only if native-inputs do not contain
>> +         ;; emacs already.  This allows us to use non-default emacs for
>> +         ;; building.
>> +         (build-inputs (if (find (match-lambda
>> +                                   (("emacs" _ ...) #t)
>> +                                   (_ #f))
>> +                                 native-inputs)
>> +                           native-inputs
>> +                           `(("emacs" ,emacs)
>> +                             ,@native-inputs)))
>
> Note that for the interpreter we normally use a keyword, here #:emacs
> (in a similar way as, say, for the python-build-system there is
> #:python).  Your code overwrites its effect in a non-transparent way.

Seconded, I prefer #:emacs, which is consistent with cmake-build-system,
python-build-system, etc.

Ludo’.

Re: [PATCH 2/6] build-system/emacs: Use "emacs" from native-inputs if specified.

[Alex Kost]

Ludovic Courtès (2016-05-20 15:00 +0300) wrote:

> Federico Beffa <beffa@ieee.org> skribis:
>
>> Alex Kost <alezost@gmail.com> writes:
>>
>>> * guix/build-system/emacs.scm (lower): Do not add "emacs" to
>>>   build-inputs if it is already specified in the native-inputs.
>>> @@ -73,8 +75,16 @@
>>>
>>>                          ;; Keep the standard inputs of 'gnu-build-system'.
>>>                          ,@(standard-packages)))
>>> -         (build-inputs `(("emacs" ,emacs)
>>> -                         ,@native-inputs))
>>> +         ;; Add emacs to build-inputs only if native-inputs do not contain
>>> +         ;; emacs already.  This allows us to use non-default emacs for
>>> +         ;; building.
>>> +         (build-inputs (if (find (match-lambda
>>> +                                   (("emacs" _ ...) #t)
>>> +                                   (_ #f))
>>> +                                 native-inputs)
>>> +                           native-inputs
>>> +                           `(("emacs" ,emacs)
>>> +                             ,@native-inputs)))
>>
>> Note that for the interpreter we normally use a keyword, here #:emacs
>> (in a similar way as, say, for the python-build-system there is
>> #:python).  Your code overwrites its effect in a non-transparent way.
>
> Seconded, I prefer #:emacs, which is consistent with cmake-build-system,
> python-build-system, etc.

OK, I understand.  So we have to stick to a full-featured "emacs" for
emacs-build-system, right?  Or do you have ideas how we could use
"emacs-minimal" as the default emacs for building, and replace it with
the full "emacs" for particular packages?

-- 
Alex

Re: [PATCH 2/6] build-system/emacs: Use "emacs" from native-inputs if specified.

[Ludovic Courtès]

Alex Kost <alezost@gmail.com> skribis:

> Ludovic Courtès (2016-05-20 15:00 +0300) wrote:
>
>> Federico Beffa <beffa@ieee.org> skribis:
>>
>>> Alex Kost <alezost@gmail.com> writes:
>>>
>>>> * guix/build-system/emacs.scm (lower): Do not add "emacs" to
>>>>   build-inputs if it is already specified in the native-inputs.
>>>> @@ -73,8 +75,16 @@
>>>>
>>>>                          ;; Keep the standard inputs of 'gnu-build-system'.
>>>>                          ,@(standard-packages)))
>>>> -         (build-inputs `(("emacs" ,emacs)
>>>> -                         ,@native-inputs))
>>>> +         ;; Add emacs to build-inputs only if native-inputs do not contain
>>>> +         ;; emacs already.  This allows us to use non-default emacs for
>>>> +         ;; building.
>>>> +         (build-inputs (if (find (match-lambda
>>>> +                                   (("emacs" _ ...) #t)
>>>> +                                   (_ #f))
>>>> +                                 native-inputs)
>>>> +                           native-inputs
>>>> +                           `(("emacs" ,emacs)
>>>> +                             ,@native-inputs)))
>>>
>>> Note that for the interpreter we normally use a keyword, here #:emacs
>>> (in a similar way as, say, for the python-build-system there is
>>> #:python).  Your code overwrites its effect in a non-transparent way.
>>
>> Seconded, I prefer #:emacs, which is consistent with cmake-build-system,
>> python-build-system, etc.
>
> OK, I understand.  So we have to stick to a full-featured "emacs" for
> emacs-build-system, right?  Or do you have ideas how we could use
> "emacs-minimal" as the default emacs for building, and replace it with
> the full "emacs" for particular packages?

I think emacs-build-system should have a #:emacs parameter (just like
python-build-system has #:python), which would default to
‘emacs-minimal’.

Does that make sense?

Ludo’.

Re: [PATCH 2/6] build-system/emacs: Use "emacs" from native-inputs if specified.

[Alex Kost]

Federico Beffa (2016-05-20 10:15 +0300) wrote:

> Alex Kost <alezost@gmail.com> writes:
>
>> * guix/build-system/emacs.scm (lower): Do not add "emacs" to
>>   build-inputs if it is already specified in the native-inputs.
>> @@ -73,8 +75,16 @@
>>
>>                          ;; Keep the standard inputs of 'gnu-build-system'.
>>                          ,@(standard-packages)))
>> -         (build-inputs `(("emacs" ,emacs)
>> -                         ,@native-inputs))
>> +         ;; Add emacs to build-inputs only if native-inputs do not contain
>> +         ;; emacs already.  This allows us to use non-default emacs for
>> +         ;; building.
>> +         (build-inputs (if (find (match-lambda
>> +                                   (("emacs" _ ...) #t)
>> +                                   (_ #f))
>> +                                 native-inputs)
>> +                           native-inputs
>> +                           `(("emacs" ,emacs)
>> +                             ,@native-inputs)))
>
> Note that for the interpreter we normally use a keyword, here #:emacs
> (in a similar way as, say, for the python-build-system there is
> #:python).  Your code overwrites its effect in a non-transparent way.
>
> Please use the keyword in the packages where you need an emacs package
> different from the default one, or remove all the code related to the
> keyword.  If you opt for the second one, please be consistent and do the
> same for all other build systems.

Oh, silly me, now I understand how this keyword works, thanks a lot for
the explanation!  I will adjust this patchset accordingly.  Please
ignore the previous message I sent to this thread :-)

-- 
Alex

[PATCH 0/6] Modifications in building emacs packages.

[Alex Kost]

Hello, currently we use either 'emacs' or 'emacs-no-x' to build
(byte-compile) emacs packages.  What about making a really minimal emacs
to use for this task?

Most of the times it should be enough.  AFAICT the only case where a
full-featured emacs is needed is auctex; and for this particular case,
'emacs-build-system' uses 'emacs'.  Instead I suggest to use
'emacs-minimal' by default; and when a full 'emacs' will be needed, it
can be specified in native-inputs.  WDYT?

Another change made by this patchset is moving all "emacs" inputs to
'native-inputs'.  There is no point to use 'inputs' because this emacs
is used only to make *.elc files and to generate autoloads; you will use
emacs from your profile anyway.

[PATCH 1/6] gnu: Add emacs-minimal.
[PATCH 2/6] build-system/emacs: Use "emacs" from native-inputs if specified.
[PATCH 3/6] build-system/emacs: Use 'emacs-minimal' as default emacs for building.
[PATCH 4/6] gnu: emacs-auctex: Use 'emacs' for byte-compiling.
[PATCH 5/6] gnu: Move emacs for building from inputs to native-inputs.
[PATCH 6/6] gnu: Use 'emacs-minimal' instead of 'emacs-no-x'.

[PATCH 2/6] build-system/emacs: Use "emacs" from native-inputs if specified.

[Alex Kost]

* guix/build-system/emacs.scm (lower): Do not add "emacs" to
  build-inputs if it is already specified in the native-inputs.
---
 guix/build-system/emacs.scm | 14 ++++++++++++--
 1 file changed, 12 insertions(+), 2 deletions(-)

diff --git a/guix/build-system/emacs.scm b/guix/build-system/emacs.scm
index 03c1eb2..017e6ef 100644
--- a/guix/build-system/emacs.scm
+++ b/guix/build-system/emacs.scm
@@ -1,5 +1,6 @@
 ;;; GNU Guix --- Functional package management for GNU
 ;;; Copyright © 2015 Federico Beffa <beffa@fbengineering.ch>
+;;; Copyright © 2016 Alex Kost <alezost@gmail.com>
 ;;;
 ;;; This file is part of GNU Guix.
 ;;;
@@ -25,6 +26,7 @@
   #:use-module (guix build-system)
   #:use-module (guix build-system gnu)
   #:use-module (ice-9 match)
+  #:use-module (srfi srfi-1)
   #:use-module (srfi srfi-26)
   #:export (%emacs-build-system-modules
             emacs-build
@@ -73,8 +75,16 @@
 
                         ;; Keep the standard inputs of 'gnu-build-system'.
                         ,@(standard-packages)))
-         (build-inputs `(("emacs" ,emacs)
-                         ,@native-inputs))
+         ;; Add emacs to build-inputs only if native-inputs do not contain
+         ;; emacs already.  This allows us to use non-default emacs for
+         ;; building.
+         (build-inputs (if (find (match-lambda
+                                   (("emacs" _ ...) #t)
+                                   (_ #f))
+                                 native-inputs)
+                           native-inputs
+                           `(("emacs" ,emacs)
+                             ,@native-inputs)))
          (outputs outputs)
          (build emacs-build)
          (arguments (strip-keyword-arguments private-keywords arguments)))))
-- 
2.7.3

Re: [PATCH 2/6] build-system/emacs: Use "emacs" from native-inputs if specified.

[Ludovic Courtès]

Alex Kost <alezost@gmail.com> skribis:

> * guix/build-system/emacs.scm (lower): Do not add "emacs" to
>   build-inputs if it is already specified in the native-inputs.

In theory, one could want to have Emacs both in ‘native-inputs’ (to
build .elc files, for instance) and in ‘inputs’ (for instance because
the program embeds a reference to the ‘emacs’ program.)

So I’m rather reluctant about this approach.

Did you find packages where Emacs wrongfully appears twice in the
inputs?  It might be best to fix those packages instead.

WDYT?

Thanks,
Ludo’.

Re: [PATCH 2/6] build-system/emacs: Use "emacs" from native-inputs if specified.

[Alex Kost]

Ludovic Courtès (2016-05-19 14:54 +0300) wrote:

> Alex Kost <alezost@gmail.com> skribis:
>
>> * guix/build-system/emacs.scm (lower): Do not add "emacs" to
>>   build-inputs if it is already specified in the native-inputs.
>
> In theory, one could want to have Emacs both in ‘native-inputs’ (to
> build .elc files, for instance) and in ‘inputs’ (for instance because
> the program embeds a reference to the ‘emacs’ program.)

I don't see a problem here, if "emacs" should be added to inputs, it may
just go there.  Nothing prohibits it.

> So I’m rather reluctant about this approach.
>
> Did you find packages where Emacs wrongfully appears twice in the
> inputs?  It might be best to fix those packages instead.

Do you mean: appears both in "inputs" and "native-inputs"?  If so, then
no, there are no such packages.

But I don't understand how this concerns.  The purpose of this patch is
to allow us to use a different "emacs" to build emacs packages.  I
would say this is the core patch of the whole patchset.  I didn't like
the fact that emacs-build-system uses a full-featured (and heavy on
dependencies) "emacs" package, and I would like to use "emacs-minimal"
instead.  But for some rare cases (currently only for auctex),
"emacs-minimal" (or "emacs-no-x") is not enough, so it should be
substituted somehow.  That's why I made this patch.

-- 
Alex