On May 1, 2012, at 03:58, Colin A. Smith wrote: > 1) The person who handles the releases would need to purchase their own > individual Mac Developer membership, create a private key, obtain a signing > certificate from Apple, and then use both the private key and signing > certificate to sign BibDesk for releases.
Does the cert expire every year, or would it be good for a longer time? I'm reluctant to cough up $100 every year to Apple for my software projects (which are already a resource sink). > If someone does get their own Mac Developer program membership, then they > could also submit BibDesk to the Mac App store Using NSTask should be enough to keep it from being accepted, but it also uses private API. Not to mention that filesystem access for linked files would make it impossible to sandbox, if I understand correctly. http://vallettaventures.com/post/20458410521/the-sandbox-banning-latex-from-the-mac-app-store -- Adam ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Bibdesk-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
