Change History (3)
comment:1 by , 19 years ago
| Description: | modified (diff) | 
|---|---|
| Resolution: | → invalid | 
| Status: | new → closed | 
comment:2 by , 19 years ago
| Resolution: | invalid | 
|---|---|
| Status: | closed → reopened | 
"so the quotes are required in the case of our udev rules."
The report was made because there are no quotes.
Ref: http://linuxfromscratch.org/pipermail/lfs-dev/2006-September/058317.html
You have contradictory statements for the reason of "closed (invalid)"
When it is clarified that no quotes are a requirement due to the splitting of long lines then the reference above still needs to be resolved and the NOTE: updated as it is not just associated to the line continuation character in the example ???
Or the opposite.
Either way, ISTM the reason for this difference in presentation is not well documented.
Thanks,
Peter
comment:3 by , 19 years ago
| Resolution: | → fixed | 
|---|---|
| Status: | reopened → closed | 
Should be done in r7798.
These files require EOF to be unquoted.


If EOF is unquoted, shell expansion occurs within the here-document. Additionally, as bash(1) states, newline handling differs between the quoted and unquoted cases, so the quotes are required in the case of our udev rules.