A structured text file that provides build and installation information for a software to be packaged in an RPM with the rpmbuild command.
Specfiles are the files that tell the rpm and rpmbuild programs which are the sources for one (or more than one) package, how to build, with which dependencies, where to install, additional scripts to execute on install/uninstall and so on.
However, the GCC driver also knows Spec Files to control the behavior of the backend tools (e.g. cc1, collect2). Same name, completely different scope.
It would seem to me (but I'm no tag expert) that it would make sense in a question to give either specfiles along with rpmbuild or specfiles along with gcc to avoid ambiguity.
However, the tag Wiki still refers to just one particular use (RPM). And old some old questions may not have rpmbuild but may have rpm or perhaps there are some that already used the tag in the GCC sense.
While GCC calls them "Spec Files" the suffix is commonly .specs, so adding specsfiles or something like gcc-specs (or gcc-specfiles) could be an option. Of course the former may create confusion with the existing specfiles. Last but not least one could split the tag into two and create gcc-specfiles and rpmbuild-specfiles or similar.
So this is why I turn to the community to ask: how to proceed with a tag whose name could refer to multiple topics, but currently only one of these topics is covered according to the tag Wiki.
Browse other questions tagged discussion tags tag-wiki tag-disambiguation .
Ambiguous tags: how to proceed in general?