Hi Bill,
There are many things that aren’t / weren’t helpful, but it’s not really
productive to rehash the past is it. While the svn switch works for the source
side (sort of), it breaks the build tree. It too can be cleaned, manipulated,
or simply deleted and rebuilt. I made a choice, one that was logical given the
severity of disruption to the original structure.
As far as I am aware, there is no requirement to use the build script for “real
development”. The tool chain is there to use, or not, as one see’s fit. I made
it plainly clear what the outputs would be, and went as far as providing
exacting examples. I don’t know how much clearer I could have made things.
The layout—even now--differs from one branch to the next which transends the
new Trunk, Branches, and Tags layout. The names of the folders differ from
branches to tags. The trunk doesn’t have subfolders, it’s basically flat until
a branch is created. To say it’s a simple svn switch from one structure to
another is just not accurate. Sure, in some circumstances, it may very well be,
but not if they were using these scripts to begin with. The least disruptive
path forward was the one I chose.
73’s
Greg, KI7MT
From: Bill Somerville [mailto:[email protected]]
Sent: Sunday, May 27, 2018 1:34 PM
To: [email protected]
Subject: Re: [wsjt-devel] SourceForge repository changes
Hi Greg,
that may be what was intended but it isn't very helpful for the few JTSDK users
that do real development. The consequence of the change in workspace location
is that their incomplete work has been orphaned with the latest JTSDK checking
out a whole new fresh workspace and building from hat rather than their
existing workspace with work in progresss.
I had assumed that the changes to accomodate the new repository layout would
adjust any checkout commands to checkout/update exactly the same workspace
contents. The `svn switch` command I gave was all that was necessary to do that
so long as any checkout command placed the workspace at the same local disk
path.
73
Bill
G4WJS.
On 27/05/2018 18:23, Greg Beam wrote:
Hi Bill, Charlie,
JTSDK is doing exactly what It is intended to do; it is checking out to:
C:\JTSDK\src\wsjtx\{trunk, branches, tags}
I posted both screenshots of, and wrote out the new paths in the upgrade email
I posted. I don’t understand how it is not working as expected.
73's
Greg, KI7MT
-----Original Message-----
From: Bill Somerville [mailto:[email protected]]
Sent: Sunday, May 27, 2018 8:08 AM
To: [email protected] <mailto:[email protected]>
Subject: Re: [wsjt-devel] SourceForge repository changes
Hi Charlie,
I will guess that the JTSDK is not quite right and is checking out the WSJT-X
sources in C:\JTSDK\src\wsjtx\trunk instead of C:\JTSDKsrc\wsjtx as used
previously. You need to delete the new trunk directory and all its contents.
I'm not sure what JTSDK changes are needed to fix it so that it uses the
correct workspace directory and builds from it.
------------------------------------------------------------------------------
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
