Re: SplitForks, AppleDouble and pax
site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com I suggest filing a bug with that request. Yup. <rdar://problem/4127860> [SplitForks] Permissions issue with resulting files -pmb _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... At 11:10 PM +0200 10/5/05, Stéphane Sudre wrote: o Is there any plan to open source the SplitForks Dev Tools? . The version in 10.2 is buggy. It does not split folder forks. . The version in 10.4 might be buggy (The permissions looks wrong after splitting a folder). While it might not be really complex to write your own SplitFork tool, fixing the Apple one could prove useful. And it might let people distributing this tool independently. (BTW: Is Apple really the company that created the AppleDouble File Format? Because when you search for AppleDouble on the Apple Developer web site, you do not find any documentation on the AppleDouble file format and not a single link to a documentation. I know there's a RFC about it but I've read better RFCs than this one). Heh. Yeah, AppleDouble was created by Apple, but its poor documentation probably has to do with how long ago it was created. The BBS era. o Is there any plan to open source the pax tool or provide a readable (read: easy to understand) man page? pax is part of the BSD distribution, and as such I think is already open source. . Trying to figure out how to extract a file from a cpio-paxed archive is not easy when you read the man page. There should be plenty of random documentation on the Internet at large of AppleDouble and the CPIO format, since both are open standards. Better (or any!) documentation of AppleDouble on *.apple.com would be another excellent topic for a bug report and/or a DTS request. This email sent to site_archiver@lists.apple.com
participants (1)
-
Peter Bierman