On Jul 28, 2006, at 2:57 PM, stephen joseph butler wrote:
> 2006/7/28, Stéphane Sudre <email@hidden>:
>> I have no doubt Apple is following the guidelines. The fact is
>> that I'm
>> looking at a workaround for a funny issue involving a CVS server,
>> where
>> a '\r' is switched to '\n'.
>
> This is your CVS server? You can checking a file as binary in order to
> prevent CVS from doing line ending translation. More here:
>
> http://ximbiot.com/cvs/manual/cvs-1.11.6/cvs_9.html
Wouldn't this also prevent diffs and merges? Ouch.
I don't work with CVS much, but diffs yes and I guess it would force a
manual merge. There's two options here:
1) hack the plist generating code strictly to work around a problem in
your development environment (while possibly producing other problems
and non-standard behavior in the release), or
2) use the binary mode of CVS as intended for these situations.
Personally, I find (1) unacceptable and (2) a reasonable compromise.
Also, I'd be worried -- in general -- that CVS's merge procedure
wouldn't always produce a valid XML file.
But it's really up to Stéphane and his own balancing act. I'm just
pointing out a possibly acceptable solution.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
