unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: divoplade <d@divoplade.fr>,45133@debbugs.gnu.org
Subject: [bug#45133] Add ocaml reactiveData
Date: Wed, 09 Dec 2020 10:40:52 -0500	[thread overview]
Message-ID: <071FCE1F-5CBA-47E3-98B2-952FFFFAE217@lepiller.eu> (raw)
In-Reply-To: <d9e3259f2a51b29f4cee5503a347dfb1774bd47e.camel@divoplade.fr>

[-- Attachment #1: Type: text/plain, Size: 620 bytes --]

There's no reason not to use the latest release. Could you scnd an updated patch for the latest release, with a comment saying future versions will use dune?

There seem to be some whitespace issues with your patch. Tabs?

Le 9 décembre 2020 09:58:35 GMT-05:00, divoplade <d@divoplade.fr> a écrit :
>Dear guix,
>
>I want to have js_of_ocaml into guix. Here is a dependency of it,
>reactiveData. It is a simple package, but the build system changed from
>ocaml-build-system to dune-build-system between the last release and
>now, so I think we should use the latest commit.
>
>Best regards,
>
>divoplade

[-- Attachment #2: Type: text/html, Size: 882 bytes --]

  reply	other threads:[~2020-12-09 15:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09 14:58 [bug#45133] Add ocaml reactiveData divoplade
2020-12-09 15:40 ` Julien Lepiller [this message]
2020-12-09 17:03   ` divoplade
2020-12-09 17:59     ` zimoun
2020-12-09 18:05       ` divoplade
2020-12-09 18:35         ` zimoun
2020-12-09 19:12           ` Julien Lepiller
2020-12-10 12:41             ` zimoun
2020-12-10 12:49               ` divoplade
2020-12-10 12:42             ` divoplade
2020-12-10 13:53               ` Julien Lepiller
2020-12-10 14:12                 ` divoplade
2020-12-10 14:43                   ` zimoun
2020-12-10 14:57                     ` divoplade
2020-12-15 14:49                       ` bug#45133: " Julien Lepiller

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=071FCE1F-5CBA-47E3-98B2-952FFFFAE217@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=45133@debbugs.gnu.org \
    --cc=d@divoplade.fr \
    /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).