site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com Thread-index: Aca8DpYS1GwYPigBEdu/oAANk0QgEg== Thread-topic: history of ditto (was: First timer: Finder Copy vs. cp) User-agent: Microsoft-Entourage/11.2.5.060620 on 8/9/06 4:27 PM, Godfrey van der Linden at gvdl@mac.com wrote:
ditto is about very efficient reproduction of a directory tree from one place onto another possibly partially populated tree. The key word is efficient, i.e. fast. It is very highly optimised and is used in the Apple build procedure, you may have noticed that the open source is in several projects. Apple builds an image by, building each of the some 1500 projects, into a directory tree known as a project root. Then they 'ditto' the project root onto a image root, adding layer after layer of projects until the final image is made.
Finally ditto was written when the only reliable way of copying file meta-data was to use tar c dir | (cd target; tar x), which is what it is designed to emulate.
Godfrey
On 10/08/2006, at 09:16 , Jeffrey Ellis wrote:
Okay, so I guess this is my next question. If cp does everything, why would anyone use ditto? I always thought that was used because of it's ability to copy resource forks.
Hi, Godfrey-- I actually just saw Finlay Dobbie's post to darwin-dev a couple of years ago saying ditto is part of BOM which is closed. Do you actually know where to find the ditto source? (Or for that matter cp?) Thanks :) All My Best, Jeffrey _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com