it seems that in spec files comments started with '#' sometimes work and sometimes don't work. For example, this line doesn't cause any problem: min-version = 2021a # due to _() but a line like the following does: gui-main = some_public_func # just this one Namely, I get an error saying unknown public function. But if I move the comment to a new line, everything works. Now, I can live with inline comments not being allowed there, but the error message is misleading and I'm not sure that the aim is really not to support comments, maybe this is just a side effect of some bug.

Am 23.07.2022 um 02:02 schrieb Cottrell, Allin: > On Fri, Jul 22, 2022 at 8:47 AM Sven Schreiber <svetosch(a)gmx.net&gt; wrote: >> it seems that in spec files comments started with '#' sometimes work and >> sometimes don't work. For example, this line doesn't cause any problem: >> > There's no bug, just no specific intent to accept #-style comments > (or any style of comments). This is not hansl, and the packaging doc > doesn't mention comments in a spec file. Ahem, that's not really true: "Blank lines are ignored, as are lines beginning with the hash mark (#), which can be used to insert comments. " (chapter 4) But I take that to mean that only complete lines can be used for commenting, no trailing comments, which is fine. And that did work for me alright.