It's not really breaking the builds...it builds from the trunk path just
fine....it's just different than it used to be is all.
Just to be sure I reinstalled JTSDK...it checks out into JTSDKsrc\wsjtx\trunk
and builds OK.
de Mike W9MDB
On Sunday, May 27, 2018, 4:12:09 PM CDT, Greg Beam <[email protected]>
wrote:
Hi Bill,
I don’t really don’t have anything further to add to this conversation. I know
what I was experienced, and fully understand the mechanics of svn switch.
If something in the scripts I’ve written is breaking the builds, I will
certainly address the issue promptly. Baring that, I don’t see this as
productive.
73’s
Greg, KI7MT
From: Bill Somerville [mailto:[email protected]]
Sent: Sunday, May 27, 2018 2:52 PM
To: [email protected]
Subject: Re: [wsjt-devel] SourceForge repository changes
On 27/05/2018 21:32, Greg Beam wrote:
While the svn switch works for the source side (sort of), it breaks the build
tree.
Hi Greg,
absolutely not, the switch is benign as it switches the repo location related
to the sources to exactly the same sources i.e. their new repo location. It
should have no impact whatsoever on the build tree. Conversely orphaning any
work in progress has the worst possible impact on the build tree as it ignores
exactly that work in progress.
The repo layout is consistent now, the use of the trunk as the "trunk" and
sibling branches and tags directories for multiple branches and tags is the
recommended layout for multiple projects in single repo. For more details see
here:
http://svnbook.red-bean.com/en/1.7/svn.reposadmin.planning.html#svn.reposadmin.projects.chooselayout
I suspect you are misunderstanding the power of the "svn switch" command, it is
able to recognize when the old and new repository paths have a common ancestor,
as any branch and tag withng a project will have with each other and with the
trunk of the same project, and do exacly what is needed to move smoothly and
accurately between them. I do this all the time and have none of the issues you
are stating.
Regardsless of the above, the required switch was from the old repository path
of some source files to the new location of the same source files.
If the defect is not going to be corrected then those with work in progress
have two options, either manually move all their modiied files additions and
deletions to the new local disk location or not use the JTSDK scripts to
orchestrate svn upadtes and builds. I suspect the former is going to be ok for
the majority, let's hope no one was working on a major submission with many
changes.
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]
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
