Greetings to all,
Our code builds on multiple platforms, and we have a target in the Makefile that copies the files to the "right places" and generates a tarball for moving from one platform to the next.
Now, under OSX prior to 10.4, this was fine. Since 10.4, tar and cp have been "enhanced" to ensure the resource fork of the source files are also copied into the tarball, or to the new location.
Which means that under *nix or win32 we end up with a lot of "._.whatever" files littering the place up. Ditto for cp's or mv's to samba or nfs mounts.
So, the question is this: Is there an option I can pass to tar and cp that will persuade them that I really don't want them to do that, since the forks aren't useful on the other platforms? The man page seems silent on the issue, beyond stating that since 10.4 they will do this...
Or: any alternate way to get the "right thing"? At present we just use find to seek and destroy all the "forks" on the non-HFS platforms, but maybe there's a better way?
Weird. Now that I've typed this, I have a strange Deja Vu that I typed this email before...
Cheers,
--
Ian
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Unix-porting mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
