|
From: | Paul Snively |
Subject: | Re: [Gnu-arch-users] Ruminations on Arch Desiderata |
Date: | Wed, 17 Sep 2003 07:15:08 -0700 |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Stephen! On Tuesday, September 16, 2003, at 11:18 PM, Stephen J. Turnbull wrote:
I know it seems counterintuitive, but as Tom quite rightly pointed out, manipulating these files wouldn't make any sense. On the CVS side, where you have no choice but to make the distinction between text files and binary files anyway, the CVS clients that use AppleSingle just declare them binary and are done with it. The upshot is that what happens when you update your project comes down to deciding whether to overwrite your binary files with whatever's newer in the repository or not. In practice, this burden isn't onerous--so little so that I have MacCVSPro configured to always overwrite binary files with newer repository content.Oh, that comment, plus your remark to Tom about "binary files" makes things clearer. I didn't realize you didn't intend to actually do any revision control manipulations (diff/patch/merge) on these files, just store them in an arch archive. In that case, just look in the vu module of hackerlab, and maybe the pfs-* files of tla/libarch. Wrapping your favorite libAppleSingle in the vu API should be straightforward, and accomplish that. I still find it hard to believe that ... is that what you meant?
So there's a vu API supported by the various pfs-* implementations, eh? That's very helpful--thanks!
--Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPANAsk not how you can "do" free software business; ask what your business can "do for" free software.
Best regards, Paul -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (Darwin) iEYEARECAAYFAj9obHYACgkQugPBK9Deter8yQCg6hzMDgp36vK3iOHolNudR3sc tn0AoMnTXVV/rz9JHc1q4t3IPMaOjOrP =mIBH -----END PGP SIGNATURE-----
[Prev in Thread] | Current Thread | [Next in Thread] |