Hi Richard

I like having the option of a package build, as I can then transfer the
installer to second machine within the household.

73

Charlie G3WDG



>
> I did that even made videos and posted them on facebook even though Gregs
> instructions are more than adequate.
> I had a friend who started to distribute and I got grief for teaching him.
> I have even used teamviewer to setup JTSDK on peoples computers buut since
> the grief I have not done this.
> Helping is a double edged sword if one of the people you help then abuses
> the system you will get the blame.
>
> I think Greg should just remove the package build option and reduce the
> problem.
>
> Richard G7OED (ex M0CLZ)
>
>
> -----Original Message-----
> From: Eric Gruff
> Sent: Monday, July 3, 2017 12:25 AM
> To: 'WSJT software development' ; 'WSJT Group'
> Subject: Re: [wsjt-devel] JTSDK Usage and Policy Guidelines
>
> Thanks, Greg. I think we all agree that we don't want to see the beta
> updates no longer made available.
>
> May I suggest to all the group users that if we see folks requesting
> install
> packages, we offer to help them set up the JTSDK environment on their
> machines, in the "teach a man to fish" spirit. They can then easily build
> the releases by typing the few magic phrases "build-hamlib3" and
> "build-wsjtx package". If they aren't willing, then they can wait for the
> official release. Those that are really motivated to get on FT8 will have
> to
> put out the relatively minimal effort.
>
> I had a few minor issues because I didn't follow directions, then started
> the install again, and it was very easy. I am happy to help if anyone
> needs
> it. I know some of you are Linux and Mac expert users, so I think we will
> have it covered.
>
> 73,
>
> Eric NC6K
>
> -----Original Message-----
> From: Greg Beam [mailto:[email protected]]
> Sent: Sunday, July 2, 2017 3:47 PM
> To: 'WSJT software development' <[email protected]>; 'WSJT
> Group' <[email protected]>
> Subject: [wsjt-devel] JTSDK Usage and Policy Guidelines
>
> Hello All,
>
> Appropriate Use
> ==============
>
> JTSDK exists to help users build and "test" Joe's software, not distribute
> it.  We all want these fantastic applications, but, we "users" must
> respect
> the developers requests.
>
> I've received several reports of WSJTX packages built with JTSDK being
> distributed by end-users. If this continues, I'll have no choice but to
> remove the package build feature from JTSDK. Joe has, on many occasions,
> requested that package installers not be re-distributed by anyone other
> than
> the development team. Please respect their wishes!
>
>
> For "Non-Developers" / "Testers" - (Setup && Usage)
> ===========================================
> For those of you "testing" Joe's software, a few things to note:
>
> * DO NOT distribute the packages you build for yourself! < nuff said >
> * Make sure, "before posting bugs", you are running the latest SVN
> revision
> * Setup JTSDK-QT as follows:
>
> - Open JTSDK-QT [1]
> - Set the following options; can be on one line separated by a " ; "
> semicolon,
> or you can set them individually. If individually, you do not need the " ;
> "
> :
>
> enable-separate ; disable-quiet ; disable-skipsvn ; enable-autosvn ;
> enable-clean ; enable-rcfg ; enable-qt55
>
> You can, if desired, enable-autorun, which will launch the newly built
> version for you.
>
> * Check your options are set properly with [2]:   list-options
> * Close, then reopen JTSDK-QT
> * Build Hamlib3:  build-hamlib3
> * Build the Release Install target (unless otherwise directed by a
> developer
> for troubleshooting):
>
> build-wsjtx rinstall
>
> You can build WSJT-X as often as you like, and should do; especially when
> new features have been added, or the development team is requesting
> broader
> use testing.
>
> * Build an installable package ( DO NO DISTRIBUTE THESE < nuff said again
> >
> ):
> * For most users, this is "not needed, nor desired for testing"
>
> build-wsjtx package
>
>
> Problems with JTSDK
> =================
>
> If you have problems with JTSDK (not WSJT-X), email me off line, and we'll
> get it sorted out.
>
> @ [email protected]
> @ [email protected]
>
> Or, post a bug on GitHub:
>
> Linux: https://github.com/KI7MT/jtsdk-nix/issues
> Windows: https://github.com/KI7MT/jtsdk-win/issues
>
>
> Documentation
> =============
>
> For Windows, documentation is available online at:
> http://jtsdk-win.readthedocs.io/en/latest/
>
> For Linux:   /usr/share/doc/jtsdk/
>
> If you find bugs in the Docs, report them to the appropriate GitHub
> location
> above.
>
>
> 73's
> Greg, KI7MT
>
> [1] main-menu.png
> [2] options.png
>
>
>
>
> ------------------------------------------------------------------------------
> 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
>
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
>
> ------------------------------------------------------------------------------
> 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

Reply via email to