Re: Mac OS X "packages" Best Practices?

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

>I'm not the original poster, but I doubt he was kidding. ... I think
>many Mac developers (myself included) would consider this a reasonable
>request.

On 02.03.2006, at 07.57 (UTC-0800), Dave Camp scribbled thusly:

>No. It's a real problem for anyone trying to place document bundles
>under source control.

I'm sorry, guys, but that's (I'm trying to think of a nice way to put this) -- right out.

Application developers are not responsible for maintaining compatiblity with source code control systems whose mechanism for tracking changes may vary wildly across different systems and even from one version of the SCCS to another. Application developers are responsible for ensuring that their products conform to the requirements of the OS upon which they run.

It is the responsibility of the SCCS developer to ensure that the SCCS works with the OSes upon which his system is expected to run. In this case, that means that Subversion should be updated to support the package model used on Mac OS X, which change could be made sufficiently generic as to be potentially useful to developers on other platforms as well.

This requires a single point of change, SVN, rather than having every Mac OS X developer on the planet rewrite his file I/O code to deal with the idiosyncracies of a single SCCS -- an interesting viewpoint, to be sure.

>If the software doesn't work right for you, you should complain.
>Sometimes things get fixed if you complain...

Yes, well, the complaint is directed at the SVN development team, then, in the form of case #707, as noted earlier.

-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 18:09:48 2006