HI Bill, On 9/25/2014 17:07, Bill Somerville wrote: > On 25/09/2014 17:50, KI7MT wrote: >> Hi Bill, > Hi Greg, >> >> On 9/25/2014 16:28, Bill Somerville wrote: >>> On 25/09/2014 15:39, Joe Taylor wrote: >>> Hi Joe, >>>> RR Bill, thanks for the update. >>> OK, I think I'm done. >>> >>> The Linux package building is still short of making compliant packages >>> but at least some sort of package (DEB and RPM) can be generated which >>> will at least install and run from in system directories (/usr) without >>> breaking anything AFAIK. >> The biggest thing I saw was the rigctld situation, which seems resolved >> now, at least for rc1 anyway. > Unless someone has an issue with it, I think shipping a hamlib 3 rigctld > called rigctld-wsjtx is just fine until the hamlib team get their v3 > release through all the hoops; given that AFAIK they haven't even > started that process yet, that will be quite some time into the future. > The need for rigctld-wsjtx is only for a very limited number of > specialized users and will not concern most WSJT-X users.
I forgot to ask, is the Build External function working now or are you taking about shipping a pre-built bianry rigctld-wsjtx ? I been messing around on Windows and havn't built on Linux in a few days. >> >> The rest of the Debian folder / packaging will need to be done manually >> anyway. > Why? >> >> >>> Nobody ever came up with better icons and graphics for the installers. I >>> must re-iterate that the ones in place were only meant as placeholders >>> and I make no claims to be a competent graphic artist. If anyone is >>> thinking of making better images I can supply the basic format, colour >>> depth, alpha channel requirements and, size parameters for each of the >>> several icons and images required by the build system for the various >>> platforms. >>>> -- Joe >>> 73 >>> Bill >>> G4WJS. >>>> On 9/25/2014 10:18 AM, Bill Somerville wrote: >>>>> On 25/09/2014 15:13, Joe Taylor wrote: >>>>>> Hi all, >>>>> Hi Joe, >>>>>> Does anyone have last-minute "must do" commits for the WSJT-X code? >>>>>> Are we converging toward tagging revision 4363 as "release candidate 1" >>>>>> for version 1.4.0 ? >>>>> I am still working through the consequences of adding in the local user >>>>> guide. There are implications for the platforms other than Windows. >>>>> There will be at least one more commit for Linux packaging and one for >>>>> Mac also I expect. >>>>>> -- Joe, K1JT >>>>> 73 >>>>> Bill >>>>> G4WJS. > 73 > Bill > G4WJS. > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > -- 73's Greg, KI7MT ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
