Hi David,
some comments in line below.
On 03/08/2020 08:35, David Spoelstra wrote:
Bill-
Yes, you are correct of course. Somehow when I changed the
"../wsjtx-2.0.0" to "../wsjtx-2.2.2" the "wsjtx-2.2.2" got cut off!
It's there in my document I wrote, so I think it was a copy/paste error.
np, I do that far too often myself.
Question: wsjt-x has brought ham radio back to life for me and I want
to give back. I'm a very rusty coder, so that's probably out. I'm a
good document writer. I also want to learn Linux packaging and I saw
someone ask about Flatpaks.
Perhaps a good place to start is a call out to the package maintainers
of Hamlib and WSJT-X, I know they exist for Debian and RPM flavours.
Perhaps they can use some help. In my experience package maintainers
look after several packages, usually because they are linking in some
way, either by area of interest or more directly.
My question is, which do you think would be the best/first package for
me to do for wsjt-x? Flatpak, snap, or appimage? Here's a comparison:
https://askubuntu.com/questions/866511/what-are-the-differences-between-snaps-appimage-flatpak-and-others
I am concerned that portable packaging is not quite mature enough yet. A
quick scan of reviews of the current popular options, and there are more
than the three shown in that summary, leaves me wondering why none of
those reviews compare performance and size with the basic RPM, Debian,
or source built installations which all run against the target systems
own dependencies. I suspect they are all avoiding the "Elephant in the
Room", hi hi.
Also, is there any place else I could lend a hand?
Well AFAIK none of these portable packaging formats need much input from
the application developers, making them just requires an application
installation, probably built from sources, against a predefined set of
dependencies. Then the whole shebang is wrapped up in a compressed
binary object that can be run on any system given certain tools are
installed.
As to which one might be best, I don't have much to help you with there,
I suspect only trying each will answer the questions. That in itself is
an issue with me, if there was just one option it would be much more
straightforward!
I should warn you that I am not greatly in favour of portable packaging
for more technical applications like WSJT-X. We are FOSS and building
from sources really isn't that big a deal, a natively installed
application will always have advantages against an imported ecosystem
that necessarily must include a bunch of dependencies which can be
readily met on the target system by a version specific package or build
form sources. To me it all seems incredibly wasteful of resources.
Thanks!
-David
73
Bill
G4WJS.
On Sun, Aug 2, 2020 at 6:07 PM Bill Somerville <[email protected]
<mailto:[email protected]>> wrote:
On 02/08/2020 21:38, David Spoelstra wrote:
> Bill-
>
> I just built 2.2.2 on Ubuntu 20.04 and noticed a few things that
> should be fixed in the INSTALL file in the 2.2.2 tarball. Some
of them
> are cosmetic. Some are actual errors if you follow the steps (line
> 131). Just my way to try and help the project!
>
> Line 13:
> Copyright 2001 - 2018 by Joe Taylor, K1JT.
> should be:
> Copyright 2001 - 2020 by Joe Taylor, K1JT.
>
> Line 34 (Debian name):
> Also qtmultimedia5-dev, libqt5libserialport5-dev,
qttools5-dev,
> should be:
> Also qtmultimedia5-dev, libqt5serialport5-dev, qttools5-dev,
>
> Line 35 (Debian name):
> libusb-1.0.0-dev
> should be:
> libusb-1.0-0-dev
>
> Line 71:
> repository e.g. wsjtx-1.9.1 by specifying it as a
variable to
> should be:
> repository e.g. wsjtx-2.2.2 by specifying it as a
variable to
>
> Line 74:
> $ cmake -D WSJTX_TAG=wsjtx-2.0.0 <source-dir-path>
> should be:
> $ cmake -D WSJTX_TAG=wsjtx-2.2.2 <source-dir-path>
>
> Line 111:
> $ cmake -D WSJTX_TAG=wsjtx-2.0.0 <source-dir-path>
> should be:
> $ cmake -D WSJTX_TAG=wsjtx-2.2.2 <source-dir-path>
>
> Line 122:
> The above commands, if successful, will produce
'wsjtx-1.9.1.tgz'
> should be:
> The above commands, if successful, will produce
'wsjtx-2.2.2.tgz'
>
> Line 128:
> $ tar xzf wsjtx-2.0.0.tgz
> should be:
> $ tar xzf wsjtx-2.2.2.tgz
>
> Line 131:
> $ cmake -DWSJT_SKIP_MANPAGES=ON -DWSJT_GENERATE_DOCS=OFF
> ../wsjtx-2.0.0
> should be:
> $ cmake -DWSJT_SKIP_MANPAGES=ON -DWSJT_GENERATE_DOCS=OFF ..
>
Hi David,
thanks for noting those issues, most had been corrected but you
picked
up a couple that had been missed, thanks.
Your last change is only correct for the WSJT-X version number, the
change to '..' for a sources path is not correct.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
