On 13.08.2018 21:53, Pierre Neidhardt wrote:
> Something else you can do it make one package inherit from the other. This
> way
> you don't need to declare the source globally.
>
That would also work but I think making it a single package is probably
the best way of handling the package.
The se
On 13.08.2018 21:23, fis trivial wrote:
> Tim Gesthuizen writes:
>
>> Hi,
>>
>> I am trying to package irony-mode for emacs and quickly
>>
>> noticed that I need more input on how packages like this should
>>
>> be seperated or handled.
>>
>
On 13.08.2018 20:11, Pierre Neidhardt wrote:
>> the server is just a work around for the missing foreign function interface
>> in
>> older emacs
> Well, Guix packages the latest Emacs, so can't you just skip the server
> altogether?
>
I guess not.
That would require rewriting the server part to m
Hi Pierre,
that was basically my question: Whether the server and the client belong
into a single package definition with a modified build procedure and two
outputs
or whether server and client should be different package definitions
because they
are quite different but dependent.
I would not
packages should be integrated.
You find the script with my package definition attached.
Mentioning packages with similar problems would also be helpful.
Best regards,
Tim Gesthuizen
(define-module (irony-mode)
#:use-module ((guix licenses) #:prefix license:)
#:use-module (guix build utils
well
as a patch for guix which I have not verified to be working attached.
It would be very nice if someone could investigate whether the patch
is ok and commit it.
Thanks,
Tim Gesthuizen
(use-modules ((guix licenses) #:prefix license:)
(guix utils)
(guix packages
