Hello David, I suggest to make a BOINC application which will consist project binaries. In this case only tasks would be downloaded. Of course if some project application will be updated then BOINC application should also be updated with the new project binaries. I understand that this way is very complicated and very bad but I think that it is the only way to do this. I do not believe that Apple guys will make an exception for BOINC project.
Thanks Best Regards, Vitalii Koshura Sent via Android 23.05.2016 11:01 пользователь "David Anderson" <da...@ssl.berkeley.edu> написал: > It would be great to have BOINC in the App Store. > However, there are items in Apple's "Review Guidelines" > that would seem to preclude BOINC: > > 2.15 Apps must be self-contained, single application installation bundles, > and cannot install code or resources in shared locations > 2.16 Apps that download or install additional code or resources to add > functionality or change their primary purpose will be rejected > 2.17 Apps that download other standalone Apps will be rejected > > See > https://developer.apple.com/app-store/review/guidelines/mac/#functionality > > It's possible that Apple would relax these rules in our case. > If anyone wants to initiate a dialog with them, please go ahead. > > -- David > > On 5/23/2016 12:46 AM, pola...@comcast.net wrote: > >> hello, >> thank you for your wonderful software. I want to ask if it is possible to >> provide this software through the Apple App store? The reason that I ask is >> because OS X provides an option for security to download software only >> through the App Store to prevent malware from being installed into the OS X >> operating system. I have read that some opensource software has been >> compromised by malware such as the Transmission bittorrent client. I >> presume that Apple does some additional security checks before releasing >> apps through the App Store. Are there copyright or patent issues or >> financial reasons that prevent you from doing this? thanks for your time >> and your efforts developing this software. >> joe >> The attachment to this e-mail as well as the content of the email itself >> may be privileged, proprietary or confidential. Do not open it. It is >> intended only for the e-mail recipient noted above. If you are not the >> intended recipient or a person responsible for delivering this >> transmission to the intended recipient, you may not disclose, copy or >> distribute this transmission or take any action in reliance on it. >> > > _______________________________________________ > boinc_dev mailing list > boinc_dev@ssl.berkeley.edu > 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 boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
