Julien Lepiller writes:
> It's not very clean, but this works:
Indeed it works ! Thanks a lot Julien.
> (define-public ocaml-mlgmpidl
> (package
> (name "ocaml-mlgmpidl")
> (version "1.2.15")
> (source (origin
> (method url-fetch)
> (uri
>
Le Wed, 20 Sep 2023 09:52:03 +0200,
Erwan Jahier a écrit :
> Hello,
>
> I am a newguix tring to package some of his software.
>
> Since I already have opam packages, I used =guix import opam=, that
> helped a little. Of course, my packages have dependancies, and not
> all of them exist in
Hello,
I am a newguix tring to package some of his software.
Since I already have opam packages, I used =guix import opam=, that
helped a little. Of course, my packages have dependancies, and not
all of them exist in the main guix repo.
I have able to build some of them (ocaml-junit, oca
Hello,
I am new to guix, and I would like to use the containers in order to have
reproducible development environments for python.
A lot of the packages that I use are not on guix yet and it would be too long
and a lot of work to actually put them as packages, hence I want to
use both guix sh
I've opened this thread to share something which I've learned with
other Guix users.
I'm currently making some modifications to the source code of zathura
, which is a PDF viewer. The original Guix package is called
=zathura=. In that direction, I've defined the following package
definition.
#+BE
Hi!
On 18 Sep 2023 at 10:50, Simon Tournier wrote:
> Re-reading, I am missing one point…
>
> [...]
>
> This wpxqqdcslxxx9g9l9j847ifgh0xdlsfl-emacs-no-x-tarball-pack.tar.gz is
> what you get before “guix pull”. It means, it used the Guix revision
> packaged by Debian (Guix v1.4 I guess).
>
> The
