HI Paul,
Originally, I had an integration setup with SF form Github. Whenever a tag hits
Gitub, it would push it to SF. It wasn’t working to well at the time. Maybe
it’s improved somewhat since then, and I’ll have another look at it.
The Clone / Download button on Github always pulls the master branch. It should
(in theory) always be runnable. I’ve not been using branching as I am the only
one working on it, but I should do really.
The branch:master pull down can list any existing branch, and has a tab for
tags. It wouldn’t’ me much trouble to add Version Info table at the top of the
README somewhere. I’ll look at that on the next update.
73’s
Greg, KI7MT
From: Paul Bramscher [mailto:[email protected]]
Sent: Friday, May 25, 2018 7:50 AM
To: Greg Beam <[email protected]>; WSJT software development
<[email protected]>
Subject: Re: [wsjt-devel] JTSDK Win32 and Nix Upgrade Available
Hi Greg--
Thanks for the update, it compiled fine on my Debian 9.4 PC -- and it built
WSJT-X rc4 8702 without trouble.
On SourceForge it was a simple matter to visually inspect which tar/gz was the
most current version and to download it. What's the best way to visually
inspect the most recently tagged/version on github?
e.g. click 'Clone or Download' and then 'Download Zip'? I see in your docs that
you have a link here: https://github.com/KI7MT/jtsdk-nix/tree/jtsdk-nix-2.0.25
Just wondering if there's a handy visual cue somewhere that I might check every
so often to see whether you've made a new release. Since I'm not an active
contributor on it, I don't benefit much from a command-line git checkout --
downloading a single zip/tar is fine for my purposes.
Thanks again,
73, KD0KZE / Paul
> On May 25, 2018 at 3:59 AM Greg Beam <[email protected]
> <mailto:[email protected]> > wrote:
>
>
> Hello All,
>
> Just a quick follow up.
>
> I pushed JTSDK-Nix v2.0.25 to Gitbub. Tested builds on WSL (18.04), VM
> (16.04 | 18.04), Native (14.04) for wsjtx-1.9.0-rc4. All passed.
>
> Attached is a couple of screen-shots from the Windows Subsystem Linux (WSL -
> Ubuntu 18.04) build. Using Xming, one could probably run WSJT-X from the WSL
> instance for testing. I'm not sure about the interoperability layer for
> com-devices, but, the UI should at least fire up.
>
> 73's
> Greg, KI7MT
>
> -----Original Message-----
> From: Greg Beam [mailto:[email protected]]
> Sent: Thursday, May 24, 2018 11:02 PM
> To: 'WSJT software development' <[email protected]
> <mailto:[email protected]> >
> Subject: RE: [wsjt-devel] JTSDK Win32 and Nix Upgrade Available
>
> Hi Paul, Bill,
>
> I didn't re-work any of the WSJT-X build scripts, so obviously the URL's
> would be wrong. As I understand it:
>
> ^wsjt/wsjt/branches/wsjtx => is still the current dev branch "I think "
> ^/wsjtx/branches/x.y.z => are historical dev branches =< 1.8 and Joe's test
> branches ^/wsjtx/tags => contain all the previous tagged branches
>
> So rc5, or whatever the future tag will be called, is living in
> ^/branches/wsjtx at present.
>
> I'm not sure I want to restructure several scripts to accommodate a
> temporary location for the current WSJT-X development branch. Fixing
> ^/wsjtx/branches and ^/wsjtx/tags is just a matter of changing two URL's in
> one script; that's already done, I just need to tag it and push it to the
> Github repo. As a result, 2/3 (for an easy description) of the WSJT-X code
> has been migrated to the new structure (^/wsjtx/branches and ^/wsjtx/tags),
> and the remaining 1/3 (for lack of a better designation) is left as was in
> ^/branches/wsjtx.
>
> I've updated the docs on SF and for Github. When the push to Github happens
> (2.0.25), that should help clear up the previous version confusion. I built
> wsjtx-1.9.0-rc4 without any trouble on my local machine. I think that is
> working as expected after the URL change for ^/wsjtx/tags.
>
> 73's
> Greg, KI7MT
>
> On 24/05/2018 13:32, Paul Bramscher wrote:
> > Thanks for the links -- I've got 2.0.24 installed using that source
> > zip, but it reports this if I try to build rc candidate
> > wsjtx-1.9.0-rc4 (and a few others that I tried):
> >
> > The following build will be run:
> >
> > * Branch ..: ^/tags
> > * Name ....: wsjtx-1.9.0-rc4
> > * Type ....: Release
> > * Target ..: install
> >
> >
> > -----------------------------------------------------
> > SVN UPDATE
> > -----------------------------------------------------
> >
> > Checking Out New Version of wsjtx-1.9.0-rc4
> > svn: E170000: URL
> > 'https://svn.code.sf.net/p/wsjt/wsjt/tags/wsjtx-1.9.0-rc4' doesn't
> > exist
> >
> > Thanks,
> > 73, KD0KZE / Paul
>
> Hi Paul,
>
> that URL is wrong, it should be
> 'https://svn.code.sf.net/p/wsjt/wsjt/wsjtx/tags/wsjtx-1.9.0-rc4'.
>
> 73
> Bill
> G4WJS.
>
>
> ----------------------------------------------------------------------------
> --
> Check out the vibrant tech community on one of the world's most engaging
> tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> wsjt-devel mailing list
> [email protected] <mailto:[email protected]>
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org!
> http://sdm.link/slashdot_______________________________________________
> wsjt-devel mailing list
> [email protected] <mailto:[email protected]>
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
