unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: 40091@debbugs.gnu.org
Subject: [bug#40091] [PATCH] gnu: dune: Update to 2.4.0.
Date: Mon, 16 Mar 2020 20:46:32 +0100	[thread overview]
Message-ID: <20200316204618.09d068df@tachikoma.lepiller.eu> (raw)
In-Reply-To: <CAEwRq=p2sWWjSUTY=1jAat-pPbY-rEbGOK-mvtNqxg7s7E=uPw@mail.gmail.com>

Thanks for the patch! I tried using it, but even though dune builds
fine, this new version removed support for jbuild, which creates build
errors when building e.g. ocaml4.07-sexplib0.

Note that according to "guix refresh -l dune" there are only 137
dependents, so this change could go to master. However, we need to find
a solution to the above issue. The guix refresh command should give you
the list of packages that depend on dune. Make sure that those who
build now still build after your patch, or fix them. We could also
duplicate the dune package and uses the older dune for our packages
that still use jbuild. Alternatively, as suggested by dune, maybe we
can try to run "dune upgrade" in these packages.

What do you think would work best?

Le Mon, 16 Mar 2020 17:44:02 +0100,
Vincent Legoll <vincent.legoll@gmail.com> a écrit :

> The added "release" make parameter, fixes the following bug:
> make: ./dune.exe: Command not found
> 
> Tested with ocaml-menhir package update
> (which will follow soon)
> 
> This may force a lot of other rebuildings, so
> may not be suitable for master
> 
> --
> Vincent Legoll

  reply	other threads:[~2020-03-16 19:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-16 16:44 [bug#40091] [PATCH] gnu: dune: Update to 2.4.0 Vincent Legoll
2020-03-16 19:46 ` Julien Lepiller [this message]
2020-03-16 20:45   ` Vincent Legoll
2020-10-15 17:03 ` zimoun
2020-11-20 21:39   ` bug#40091: " Christopher Baines

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200316204618.09d068df@tachikoma.lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=40091@debbugs.gnu.org \
    --cc=vincent.legoll@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).