On Tue, Feb 17, 2004 at 12:03:45AM +1100, Rohan Lloyd wrote: > On 16 Feb 2004, at 8:20 PM, Daniel Macks wrote: > > >Okay Rohan, I think that works now. I just patched Services.pm. Give > >it a try. For the second above, I used: > > > > # Unfold multiline commands into one line > > $script =~ s/\s*\\\s*\n/ /g; > > > >in case Maintainer got sloppy and left training whitespace after \. I > >also updated the Packaging Manual docs for Script fields (which didn't > >even mention #! scripts at all!). > > Strictly speaking the '\' should appear immediately before the '\n'. To > quote bash(1): [snip]
Yup. > I'm not sure of the benefit of allowing sloppiness. We've never cared before? No seriously, last time I advocated strict syntax parsing even when it was pretty clear what the Maintainer meant, I got shot down. Currently 667 .info files in 10.3/unstable have (non-blank) lines with trailing whitespace. We should get input from others... > If you do that you would get the strange behaviour that it would > work with individual script lines, but if they added a "#!/bin/sh" > on the first line, the shell would not recognise the continuation, > and you'd get different results. Yeah. dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
