>> 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.
I contend that applications that do not respect extra contents added
to a bundle are equally at fault. When Pages (as an example) saves
the open document, it blows away any additional files that were in
the in the document bundle instead of preserving them. It's not an
issue specific to source control. It would apply equally well to any
other process that might add a file to a document bundle.
It certainly would be nice if svn had a built in way of bypassing
this issue, but I don't have much hope for that.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 3 05:11:23 2006