Created attachment 353590 [details] ebuild showing the problem 'ebuild foo manifest' and emerge treat '#' comments differently. In the attached ebuild, in src_prepare, comment is only on one line - that causes an obvious warning during emerge ('Access denied'). However, if the comment is on both lines, 'ebuild foo manifest' bails out with 'line 30: syntax error at unexpected marker {'.
(In reply to Rafał Mużyło from comment #0) > Created attachment 353590 [details] > ebuild showing the problem > > 'ebuild foo manifest' and emerge treat '#' comments differently. > > In the attached ebuild, in src_prepare, comment is only on one line - that > causes an obvious warning during emerge ('Access denied'). That behavior is correct, since it thinks the ebuild is trying to execute the package, which is not allowed. > However, if the comment is on both lines, 'ebuild foo manifest' bails out > with 'line 30: syntax error at unexpected marker {'. This behavior is expected, since bash does not allow empty functions. I don't see anything to change here, because the things that you report are intended behaviors of bash that portage has no control over.
Rather than comment out the contents of src_prepare, you would really want to comment out the whole function, since bash doesn't allow empty function declarations.
(In reply to Zac Medico from comment #2) > Rather than comment out the contents of src_prepare, you would really want > to comment out the whole function, since bash doesn't allow empty function > declarations. OK, didn't know about "empty functions part". On not quite related note: would you mind giving bug 369581 a push ? It's still valid in 0.3.0.7.
