Would it be possible to add the usual hash-comment parsing for /etc/eselect/compiler/*.conf (or add a mention to the documentation if it's already there)? With multiple specs files and multiple ctargets, it gets a bit confusing. Allowing an admin to stick a line of hashes between the ctargets would be nice, as would be allowing comments documenting various entries. Reproducible: Always Steps to Reproduce:
Hi Duncan, this would certainly be nice, but it's not on my "needed for release" list at this point, so I'm going to be focusing on those issues. sekretarz might be willing to addd that commenting as he's the one who made the parser. If not, feel free to dive into parse_conf.c and submit a patch. I'll be more than willing to commit such a change. Thanks.
No big deal. Mainly I was wondering if it was already there and not yet documented, as I thought it might be if the parsing code had been shared in from another app (which is what open source is for, after all =8^). I'm not into C as yet (current goal is python, but it has sat, recently), so don't look for a patch from me any time soon, unless "magic happens!" =8^( Duncan
eselect-compiler is dead for now
