On Tue, Nov 7, 2023 at 4:27 PM Matt Melling via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> Hi,
>
> I am hacking on the WSJT-X package in NixOS, and looking at how we can
> split out the hamlib fork in to a separate package that can be shared
> with our js8call package.
>
On Fedora
Debian has been building wsjtx with the stock upstream hamlib for ages
without issues.
Mageia also.
We build against the system version.
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
Re: Matt Melling via wsjt-devel
> Thanks Mike l. My understanding is that at some point in the past there were
> some patches needed for Hamlib. Is that no longer the case?
Debian has been building wsjtx with the stock upstream hamlib for ages
without issues.
Christoph DF7CB
Thanks Mike l. My understanding is that at some point in the past there were
some patches needed for Hamlib. Is that no longer the case?
On 8 November 2023 00:51:00 GMT, Black Michael via wsjt-devel
wrote:
>That sourceforge link is no good anymore since Bill is SK.
>Here is the master repo
That sourceforge link is no good anymore since Bill is SK.
Here is the master repo https://github.com/Hamlib/Hamlib
And here are the packages -- https://n0nb.users.sourceforge.net/
Mike W9MDB
> On Nov 7, 2023, at 4:27 PM, Matt Melling via wsjt-devel
> wrote:
>
> Hi,
>
> I am hacking on the
Hi,
I am hacking on the WSJT-X package in NixOS, and looking at how we can
split out the hamlib fork in to a separate package that can be shared
with our js8call package.
The INSTALL references
https://sourceforge.net/u/bsomervi/hamlib/ci/master/tree/ where the
latest tag is 4.3.1. The master
