all. Maybe that
would be the best way?
-Matt / KK4NDE
-Original Message-
From: Christoph Berg [mailto:m...@debian.org]
Sent: Friday, May 10, 2019 12:21 PM
To: WSJT software development
Subject: Re: [wsjt-devel] Expiration Date on Software
Re: Adam Bartlett 2019-05-10
> One of the
Re: Adam Bartlett 2019-05-10
> One of the challenges of automatic updating is package managers and such on
> the Linux side are often generations behind (not a big deal, but if a user
> installs Ubuntu, types "apt install wsjtx" and they still have 1.x in their
> repo it's going to confuse them)
One of the challenges of automatic updating is package managers and such on
the Linux side are often generations behind (not a big deal, but if a user
installs Ubuntu, types "apt install wsjtx" and they still have 1.x in their
repo it's going to confuse them) and trying to deal with those can be
If the program on startup finds a valid Internet connection, then check for
an update automatically. If one is available, download it, or at least
supply a link to the file, and THEN allow the user to install (or delete)
it as they feel. Make it keep bugging the user on startup of WSJTx until
Backwards compatibility is a thing ...
Also, if the new version of the software knows how to decode an older
encoding, you already have an implied version number.
It's not like this takes eons to decode, nothing wrong with trying several
times, newest version first, next version next and so on.
intervention to keep things working can and will fail sooner
or later.
-Matt / KK4NDE
From: Matthew Miller [mailto:mmill...@mail.umw.edu]
Sent: Friday, May 10, 2019 7:20 AM
To: 'WSJT software development'
Cc: 'Gustafson Neil'
Subject: Re: [wsjt-devel] Expiration Date on Software
Even easier than
essage-
From: rjai...@gmail.com<mailto:rjai...@gmail.com>
[mailto:rjai...@gmail.com<mailto:rjai...@gmail.com>]
Sent: Tuesday, May 07, 2019 7:19 PM
To: WSJT software development
Cc: Gustafson Neil
Subject: Re: [wsjt-devel] Expiration Date on Software
That's a good idea. Some held
Hi Onno,
>A better idea is to include a protocol version number in the QSO information,
>that way both sides have a chance to alert the operator.
A nice idea, but that information needs to be sent using the lower layer of the
previous protocol version….
73, Reino, oh3ma
int is, for a beta the expiration makes sense like a trial expires.
>> For production software, there are much more conventional reasonable ways
>> to encourage users to update.
>>
>> -Matt / KK4NDE
>>
>> -----Original Message-
>> From: rjai...@gmai
ays
>> to encourage users to update.
>>
>> -Matt / KK4NDE
>>
>> -----Original Message-
>> From: rjai...@gmail.com [mailto:rjai...@gmail.com]
>> Sent: Tuesday, May 07, 2019 7:19 PM
>> To: WSJT software development
>> Cc: Gustafson Neil
>> S
sers to update.
>
> -Matt / KK4NDE
>
> -Original Message-
> From: rjai...@gmail.com [mailto:rjai...@gmail.com]
> Sent: Tuesday, May 07, 2019 7:19 PM
> To: WSJT software development
> Cc: Gustafson Neil
> Subject: Re: [wsjt-devel] Expiration Date on Software
>
&g
-devel] Expiration Date on Software
That's a good idea. Some held on to old versions so they could retain features
that were detrimental to the herd, such as lock rx=tx.
Expiring the versions is a very good idea.
Ria
N2RJ
On Tue, 7 May 2019 at 19:14, Gustafson Neil via wsjt-devel
wrote:
>
&
12 matches
Mail list logo
