NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
mac accessing non HFS volume (Score:2)
You can delete them immediately before packaging for distribution (or incorporate that into your packaging script). Another option would be to instruct your editor to not save resource forks for those files. Yet another option would be to work locally on an HFS volume, and then FTP the files or cp them or something that won't try to carry the resource forks over to the final destination before packaging.
-matt
Reply to This
Re:mac accessing non HFS volume (Score:2)
I'm reading from my "amigos" page which showed your earlier journal entry, but further down a ways and so I see now that you already know the cause.
never mind
-matt
Re:mac accessing non HFS volume (Score:2)
hyperstation ~/Develop/Copenhagen/modules/Games/Bingo/Bot % find . -name "._*"
hyperstation ~/Develop/Copenhagen/modules/Games/Bingo/Bot % rm -Rf
hyperstation ~/Develop/Copenhagen/modules/Games/Bingo/Bot % find . -name "._*"
hyperstation ~/Develop/Copenhagen/modules/Games/Bi
Re:mac accessing non HFS volume (Score:2)
> any problems with deletion of the resource files?
nope.
The sorts of things you might be likely to drop when working with text files include type/creator (which would go back to their default according to file extension and your OS prefs... 'get info' on a file and 'change all files of this type' to change your OS prefs) and editor nicities window size/placement and cursor/selection loction when last saved.
If you don't mind missing those sorts of details, then deleting the resource forks of text files