Re: Mac OS X "packages" Best Practices?

On 02.03.2006, at 09.56 (UTC-0800), Aaron Montgomery scribbled thusly:

>Correct, but in the Mac OS X file system, a bundle is a directory.
>If the developer wants the document to be treated as a single opaque
>object in the file system, he/she needs to create a file, not a
>directory. If the developer creates a directory, he/she should allow
>that directory to be treated like a directory.

Sorry, no, that's not the way Mac OS X works. Bundles are integral to the way applications are packaged and store data now, and they are intended to be opaque to the user. The Finder maintains this illusion (although it also allows a means by which the user can see inside the bundle if he really wants to).

No current filesystem used by Mac OS X supports bundles as such; they are always directories (or folders). It's not up to the developer whether a bundle is treated as a directory or as a file; if a bundle is needed, it's needed.

Again, it's up to the SCCS to deal with this, as it is a requirement for use on Mac OS X systems. And, as the commentary in case #707 points out, Mac OS X is not the only environment in which one might wish to have this capability. The fact that neither SVN nor, as I recall, CVS (except after some hacking by Apple) do this is extremely unfortunate, and is the primary reason I haven't put my Mac code under SVN yet, although XCode 1.2+ seems to have been modified to deal with SVN's hidden directory.

(This latter is a case in which it could be considered reasonable for the application to handle this, as XCode has integrated support for SVN and is a development tool.)

-Mike

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 2 19:12:45 2006