On Jul 18, 2006, at 6:45 PM, David M. Cooke wrote: > > You've got to explicitly handle the resource fork yourself. The tar > format (AFAIK) doesn't support any notion of extra metadata or > forks of a file. Tiger's tar fakes it by saving the resource fork > as a separate file with '._' added to the front (e.g., for > 'hello.font', it stores the data fork as 'hello.font', and the > resource fork as '._hello.font'). > > I've attached two scripts I wrote a while ago that handle the > resource forks in this way. >
David, Thank you very much for the scripts. I am just about to dig into them today. I was afraid that this would be the case. I was hoping the support for resources forks would come for free under Tiger. Again, I really appreciate the help. Reid > -- > |>|\/|< > /------------------------------------------------------------------\ > |David M. Cooke http://arbutus.physics.mcmaster.ca/dmc/ > |[EMAIL PROTECTED] > <maketar.py> > <extar.py> > _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
