Re^3: Executable bit sloppiness in modules

IME its standard practice to convert CPAN modules to unix lines endings before upload. I know that I have had to do so for all of my modules. So im not sure you can rely on the line endings as being indicitive.

For instance what mode are the modules from Data::Dump::Streamer?

---
demerphq

Comment on Re^3: Executable bit sloppiness in modules

Replies are listed 'Best First'.
Re^4: Executable bit sloppiness in modules by zentara (Cardinal) on Dec 19, 2004 at 11:44 UTC
Data::Dump::Streamer has unix line endings, but all files and directories are mode 755. I just don't like that, and makes me leary of automatic Cpan installs. It makes me want to give all the files a "look-over" first. I can see how this could be abused by introducing executable files to your system.( Like license.txt....how many people actually check it?) For instance, what if I'm a little groggy, and want to look at the README file, and accidently double click it, instead of opening it for viewing, and the first line was a system command? I just think that part of CPAN's rules, should be correct file permissions for the file types. I'm not really a human, but I play one on earth. flash japh	[reply]
Re^5: Executable bit sloppiness in modules by demerphq (Chancellor) on Dec 19, 2004 at 11:55 UTC
How do I on Win32 make sure that `nmake dist` produces a file with the correct permissions? I mean execute priviledges on Win32 dont have the same meaning as they do on Unix. So what to do when permission semantics are not platform portable? (Executable permissions on a file that isnt a registered executable type do nothing on Win32) --- demerphq	[reply] [d/l]