Re: release preparation: odd file permissions, #!'s, ^M's, and README
Mitchell N Charity [EMAIL PROTECTED] wrote: README says [ snip ] There was more outdatet stuff in there. Fixed. Mitchell leo
Re: release preparation: odd file permissions, #!'s, ^M's, and README
Mitchell N Charity [EMAIL PROTECTED] wrote: Some quick observations on parrot_2004-02-26_08. Files with ^M: [ ... ] ./t/op/00ff-dos.t Actually that one is failing on Win32!!!1 Is this caused by the test system? Which line endings do we support? The file ./testyamd probably belongs in ./tools/dev/, not in the top level directory. Moved. These files are still at 0.0.13: Will be updated RSN :) README says The list of targetted platforms can be found in docs/parrot.pod. Which has a =head2 Supported Platforms Neither mentions PLATFORMS. Yep. README says The full changelog is available as ChangeLog. But ChangeLog was last updated 2003-10-31. There are very few entries in ChangeLog recently (mainly release change summaries). It looks like that it got updated automatically til 2002-03-19. How was it done? Mitchell Thanks for your summary, leo
Re: release preparation: odd file permissions, #!'s, ^M's, and README
--- Leopold Toetsch [EMAIL PROTECTED] wrote: Mitchell N Charity [EMAIL PROTECTED] wrote: Some quick observations on parrot_2004-02-26_08. Files with ^M: [ ... ] ./t/op/00ff-dos.t Actually that one is failing on Win32!!!1 Is this caused by the test system? Which line endings do we support? The win32 version of cvs converts \n into \r\n... so that files endings become \r\r\n, which makes perl5 unable to find the end of heredocs. __ Do you Yahoo!? Get better spam protection with Yahoo! Mail. http://antispam.yahoo.com/tools
Re: release preparation: odd file permissions, #!'s, ^M's, and README
On 26 Feb 2004, at 18:57, Mitchell N Charity wrote: A perl by any other name, may be a different perl. perl and /usr/bin/perl are both common in #!'s. I been changing them to #! perl -w when i find them, which is why your list covers the places I haven't visited. The good thing about the bang line is that it's parsed by perl and thus turns on warnings. I'll use your list to standardize the rest. Mike