all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Malte Frank Gerdes <malte.f.gerdes@gmail.com>
Cc: 43852@debbugs.gnu.org
Subject: [bug#43852] [PATCH] gnu: Add riscv-openocd.
Date: Fri, 9 Oct 2020 21:02:57 +0200	[thread overview]
Message-ID: <20201009190257.GA2052@jurong> (raw)
In-Reply-To: <86lfgh6bzy.fsf@gmail.com>

Hello,

since I am speaking as someone who does not know what these packages are
about, please take what follows with a grain of salt.

On Wed, Oct 07, 2020 at 10:02:09PM +0200, Malte Frank Gerdes wrote:
> libjaylink ... is
> ... available as a package. The available package ...
> ... is too old ...
> ... should I do something?

Written like this, I would say you could try updating it, independently
of your target package. Then the question is whether you break anything
else:
    guix refresh -l libjaylink
A single dependent package: openocd@0.10.0

So there already is an openocd, which maybe should be updated at the same
time?

And do you really need a new package, or could it be enough to provide
more inputs or configuration flags to the existing one? Otherwise, how
about inheriting? The name also is weird, see the section in the manual;
we normally keep the upstream project name.

Andreas





  reply	other threads:[~2020-10-09 19:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-07 20:02 [bug#43852] [PATCH] gnu: Add riscv-openocd Malte Frank Gerdes
2020-10-09 19:02 ` Andreas Enge [this message]
2020-10-10 14:02   ` [bug#43852] [PATCH v2] " Malte Frank Gerdes
2020-10-22 14:49     ` bug#43852: " Ludovic Courtès

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=20201009190257.GA2052@jurong \
    --to=andreas@enge.fr \
    --cc=43852@debbugs.gnu.org \
    --cc=malte.f.gerdes@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 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.