Ludovic Courtès writes:
> Hi,
>
> Philip Kaludercic skribis:
>
>> Thiago Jung Bauermann writes:
>>
My fear is that with further upstream development,
there might be conflicts between the packages I inherit from (emacs,
emacs-no-x, emacs-minimal) and the packages I have definined
Hi,
Philip Kaludercic skribis:
> Thiago Jung Bauermann writes:
>
>>> My fear is that with further upstream development,
>>> there might be conflicts between the packages I inherit from (emacs,
>>> emacs-no-x, emacs-minimal) and the packages I have definined in [1].
>>> An easy fix might be to
Thiago Jung Bauermann writes:
>> My fear is that with further upstream development,
>> there might be conflicts between the packages I inherit from (emacs,
>> emacs-no-x, emacs-minimal) and the packages I have definined in [1].
>> An easy fix might be to not rely on the upstream package
Hi Philip,
If I read correctly, the repositority [1] provides many recipes which
create various Emacs VM. Cool!
Well, from my point of view, these should live in a channel. Maybe the
channel guix-past is a good location. Somehow, it would be better to
have a channel with binary substitutes.
Hello Philip,
Philip Kaludercic writes:
> reading [0], I would like to ask if there is any interest in
> up-streaming the work I have been doing to build old versions of Emacs
> using Guix (the main use-case is to help with testing Emacs packages on
> various versions)[1]?
This is a very
Hi,
reading [0], I would like to ask if there is any interest in
up-streaming the work I have been doing to build old versions of Emacs
using Guix (the main use-case is to help with testing Emacs packages on
various versions)[1]? My fear is that with further upstream development,
there might
