[Openmcl-devel] CCL and the Mac App Store

[Gail Zacharias]

Perhaps they don't plan to apply the rules to developer tools.  That would
make sense if the goal of sandboxing is to protect computer-naive users.

On Wed, Dec 21, 2011 at 3:46 PM, Alexander Repenning
<ralex at cs.colorado.edu>wrote:

> Any guesses if Apple may grandfather current App Store Apps once they
> implement their sandbox? I mean, what would they do with the 500,000 apps
> when the requirement becomes mandatory? They probably could not just throw
> existing Apps out. I guess they could, but what would they be left with?
>
> Alex
>
>
> On Dec 21, 2011, at 8:35 AM, Andrew Shalit wrote:
>
> They did not make us jump through any special hoops.  We did what the
> documentation says to do in terms of code signing, submitted, and got
> approved.
>
> By "we" I mean Matt, of course.
>
> Note that we don't know what will happen when Apple starts enforcing its
> sandboxing rules.  That's part of why we want CCL in the store: so that we
> ask concrete questions about sandbox in reference to our existing app.  But
> the potential sandboxing issues aren't related to the fact that CCL is
> written in Lisp; they're related to the fact that CCL is a development tool
> and so it wants to be able to do things like have read-write access to
> multiple files on disk, and know where its home directory is so it can load
> an init.lisp file.
>
>
>  Prof. Alexander Repenning
>
>
> University of Colorado
>
> Computer Science Department
>
> Boulder, CO 80309-430
>
>
> vCard: http://www.cs.colorado.edu/~ralex/AlexanderRepenning.vcf
>
>
>
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> http://clozure.com/mailman/listinfo/openmcl-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clozure.com/pipermail/openmcl-devel/attachments/20111221/831d64ba/attachment.htm>