Hi Richard, <snip>
This is ill advised for a number of reasons. > > "if someone tells me which > files after the build are essential to running wsjtx I make a built tarball > available." > Just to name a few: [1] Joe has asked ( on more than one occasion ) that we not re-distribute unofficial binary packages, this would clearly be an unofficial set of binaries. [2] Building packages destine for redistribution should only be done in a clean / repeatable environment ( chroot or equivalent ). Ones personal workstation hardly meets that need unless your using a chroot tool set like Cowbuilder / Sbuild / Pbuilder (for Debian based systems) or using a purpose built server like Launchpad (Ubuntu). [3] WSJT-X prebuilt ARMv7 packages are available in PPA form at present, however, they are for v1.6.0 GA Release only due to item [1]. [4] Simply transferring a pre-built set of binaries sets up the user for failure. There is a reason why a system package managers should be used for installation by non-developers. Even using dpkg will not properly resolve dependencies on a new System Installation. [5] Your more than welcome to create a PPA for development versions, but again, see item [1]. I removed all WSJT-X v1.7.x builds from public access due to item [1]. 73's Greg, KI7MT ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
