Andreas Enge <andreas@enge.fr> writes:

> 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.

Feedback is always good! especially when it leads to realizing how it
should actually be done.

> 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?

The problem was: i didn't realize that libjaylink has a new release and
that it's actually possible to clone it; because the official upstream
repo seems to be locked behind a login. But there is a mirror of it on
repo.or.cz - which i'm now using. 

> 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.

I used riscv/riscv-openocd as the upstream repo (github), but it seems
that this isn't necessary. So i'm now just updating the package we
already have. It doesn't have a new release, so i had to use the git
master.


Malte