all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jean-Pierre De Jesus Diaz <jean@foundation.xyz>
To: Antero Mejr <mail@antr.me>
Cc: 73237@debbugs.gnu.org
Subject: [bug#73237] [PATCH] gnu: Add coq-ceres.
Date: Mon, 16 Sep 2024 15:19:31 +0000	[thread overview]
Message-ID: <CAG1gdUqp6u=2kuVBhCFsdFSODYR7+XjVdWatq8AUXgVNC3MnnA@mail.gmail.com> (raw)
In-Reply-To: <87o74nr5p6.fsf@antr.me>

>Yes. For some reason, the coq-mathcomp-bigenough package propagates coq,
>and coq-stdpp has it in inputs, so I was unsure where to put it. I think
>those packages should be updated to have coq as a native-input as well.

That's odd, it also propagates `which' when it shouldn't, only coq-mathcomp
should be propagated.

On Mon, Sep 16, 2024 at 3:14 PM Antero Mejr <mail@antr.me> wrote:
>
> Jean-Pierre De Jesus Diaz <jean@foundation.xyz> writes:
>
> > I've also recently packaged coq-ceres for Guix in my personal channel,
> > it is a shorter version:
>
> There's a lot of useful stuff there, it would be great to get it
> upstreamed. Unfortunately I do not have commit access.
>
> > I'd also adapt the install-doc to use the install-doc target of the generated
> > Makefile like this:
>
> That sounds good, I will update the patch.
>
> > Coq does not need to be propagated, only needs to be a native-input.
>
> Yes. For some reason, the coq-mathcomp-bigenough package propagates coq,
> and coq-stdpp has it in inputs, so I was unsure where to put it. I think
> those packages should be updated to have coq as a native-input as well.




  reply	other threads:[~2024-09-16 15:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-13 20:55 [bug#73237] [PATCH] gnu: Add coq-ceres Antero Mejr via Guix-patches via
2024-09-16 14:54 ` Jean-Pierre De Jesus Diaz
2024-09-16 15:14   ` Antero Mejr via Guix-patches via
2024-09-16 15:19     ` Jean-Pierre De Jesus Diaz [this message]
2024-09-16 15:30       ` Jean-Pierre De Jesus Diaz

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

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

  git send-email \
    --in-reply-to='CAG1gdUqp6u=2kuVBhCFsdFSODYR7+XjVdWatq8AUXgVNC3MnnA@mail.gmail.com' \
    --to=jean@foundation.xyz \
    --cc=73237@debbugs.gnu.org \
    --cc=mail@antr.me \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.