Hello all, 1 - I have a copy of WindowsBuildDependencies for VS 2013 (not up-to-date but anyway) and I think I can update needed binaries and build them (even update the project to VS 2015 and/or VS 2017). It looks like an interesting and challenging task for me. 2 - ISM files are files for InstallShield installer ( https://en.wikipedia.org/wiki/InstallShield). It is a proprietary tool and a license is very expensive but I can rewrte the installer using some free tools (e.g. NSIS because I worked with this tool some time). This task also looks very interesting and challenging for me.
So possibly I can help with this if you will give me suh opportunity. Thanks Best regards, Vitalii Koshura 2016-12-06 17:23 GMT+02:00 Richard Haselgrove <[email protected]> : > I would agree with making v7.6.33 the recommended download - after all, it > is now over six months since it was made available for testing. > But that also raises a major question about future client development and > deployment - a question which is perhaps better addressed to the Project > Management Committee as a whole, rather than to David as an individual. > How are any future changes found to be necessary or desirable in the BOINC > client going to be made available to volunteers - I'm thinking specifically > in the Windows case. > That's a three-stage process:1) Build new binaries2) Package them into an > installer3) Distribute them via a trusted channel > At the moment, even the build stage is problematic: despite Christian's > assistance on the BOINC message boards a month ago, none of the build > dependency sets listed on http://boinc.berkeley.edu/ > trac/wiki/SourceCodeGit#Windowsbuilddependencies is currently accessible. > I don't think the tools for updating the Windows installer have ever been > exposed for community use (there are ISM files in the 'installerv2' folder > available from github, but I have never found any documentation for how > they might be maintained and used by the community). > For many years - see for example github issue 792 and its predecessor > trac ticket 815 - windows installer issues have been deferred to 'the new > open source installer'. I would suggest that the PMC should look at all > issues - including funding - relating to recruiting and empowering somebody > with the necessary skills to re-invigorate and manage the build/deployment > section of the development process. > > On Tuesday, 6 December 2016, 10:47, Filip Rydlo <[email protected]> > wrote: > > > Hi, David and all. > No objections here too. :-) > > Running *7.6.33* (x64) for *loooooooooooong* time > a) on *Windows 10* (at work) and > b) on *Windows 7* *Prof.* (home) > both: without any problems. > > > > Filip R. > P.S. What is the specialization of Rom? I could learn it and then do it! > More specifically FROM date: *2017-04-02 ...... > **indefinitely, > till I'll be alive. :-)* > > > > > 2016-12-06 1:15 GMT+01:00 David Anderson <[email protected]>: > > > Anyone object to making 7.6.33 the recommended version? > > It has 96% test coverage, and the only significant reported bug is a > > problem with GPU detection > > with new NVIDIA drivers, which I think is independent of client version. > > -- David > > > > > > -------- Forwarded Message -------- > > Subject: Update recommended client to latest available > development? > > Date: Fri, 18 Nov 2016 11:31:51 +0100 > > From: Jord van der Elst <[email protected]> > > To: David Anderson <[email protected]> > > > > > > > > Hi David, > > > > Can we have the latest available recommended client from the Download > > pages be set to 7.6.33 for both Mac and Windows, please? As this solves > > quite a bit of problems for users out there with Windows 10 and Mac OS X > > Sierra. > > > > And I'd rather have that version available than the slightly more broken > > ones before that. > > Especially since I doubt we'll have a new client in the foreseeable > future > > anyway, with Rom having moved out. > > > > Should I leave Rom as moderator/project developer on the boards? > > > > Thanks, > > > > > > -- Jord van der Elst. > > _______________________________________________ > > boinc_dev mailing list > > [email protected] > > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > > To unsubscribe, visit the above URL and > > (near bottom of page) enter your email address. > > > _______________________________________________ > boinc_dev mailing list > [email protected] > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. > > > > _______________________________________________ > boinc_dev mailing list > [email protected] > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. > _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
