[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: experiment to get Mac resource-forks under version control [with PATCH]

From: Julian Reschke <julian.reschke_at_gmx.de>
Date: 2003-05-14 09:18:00 CEST

> From: Nicholas Riley [mailto:njriley@uiuc.edu]
> Sent: Wednesday, May 14, 2003 8:51 AM
> To: Scott Collins
> Cc: dev@subversion.tigris.org
> Subject: Re: experiment to get Mac resource-forks under version control
> [with PATCH]
> ...
> I feel the same way, FWIW. We need more metadata, not less. If it
> has to be implemented in a not-so-nice way on foreign filesystems, so
> be it. Other Unixes and Windows are moving towards extended
> attributes in -their- native filesystems (in the case of NTFS, it
> already exists), which Subversion will need to support eventually - so
> it won't be a permanent discontinuity. And the fact is, simply, that
> many components written since the release of OS X use resource forks
> for metadata. The "all the world's UFS" mentality is backwards-thinking.

That being said -- if you *really* want to put Mac resource forks into
properties, you should probably extract all properties from the resource
fork and treat each one as a *separate* DAV/SVN property. That way
non-Mac-specific clients could take advantage of it as well (as far as I
remember each one has a 4-ASCII-letter code, so you could easily map them to
custom properties in a "Mac resource fork" namespace).


<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 14 09:19:00 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.