| 1 |
On Mon, 2021-06-28 at 16:52 +0200, Michał Górny wrote: |
| 2 |
> > |
| 3 |
> > This is long overdue, for many reasons, but in particular it would |
| 4 |
> > force us to declare a dependency on a C compiler if one is needed and |
| 5 |
> > allow you to re-test only those packages that use a C compiler. |
| 6 |
> > |
| 7 |
> |
| 8 |
> Which C compiler? The one I have in CC for the package in question, or |
| 9 |
> the one selected via gcc-config, or any random C compiler that might not |
| 10 |
> be used at all? Does that mean that if clang is pulled via depgraph, |
| 11 |
> Portage will insist on depcleaning gcc by default? |
| 12 |
> |
| 13 |
|
| 14 |
If the package declares a dependency on e.g. virtual/c-compiler, ago |
| 15 |
would want to re-test it whenever a new version of any compiler is |
| 16 |
released that satisfies virtual/c-compiler. Conversely, if the package |
| 17 |
doesn't require virtual/c-compiler, we may assume that it doesn't |
| 18 |
compile C code, and is not affected by the new version. |
| 19 |
|
| 20 |
I know switching toolchains is a mess at the moment, but independently |
| 21 |
adding (correct) dependency information should make many things easier |
| 22 |
without harming anything else. The precise nature of the dependencies |
| 23 |
would of course need some thought. |
Archives