On 02/28/2018 04:28 PM, Orcan Ogetbil wrote:
On 28 February 2018 at 09:19, Nicolas Mailhot wrote:
My point was *non-C-compilers* can read *C/C++* header files because they
need to read the ABI definitions to use it from their non C/C++ code.
That makes a C/C++ header file consumable by pretty much any kind of
compiler, so it's *completely useless* to try to make C/C++ devel packages
pull in a compiler, via virtual provides or not.
Hello,
These are all _very_ edge use-cases. The primary use is to build the
software. Hence pulling in a compiler will not be quite harmful; it is
certainly not *completely useless*.
On the other hand it will clear up vast majority of the build
failures. I was trying to come up with the least intrusive solution.
The headers don't *require* any damn thing, except perhaps other headers
(from other -devel packages). They are generally *used by* C/C++
compilers, but there are all sorts of other users (including humans just
looking at it) too as has been pointed out.
Point being, "used by" and "requires" are two very different kind of
dependencies.
- Panu -
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
