* Guillem Jover <[email protected]> [260301 16:13]:
This had been burning in the back of my head for a while, but then I though I had misread the delegations and dropped it. But with the new appearance of a "FIXME-IN-THE-SOURCE-SECTION" section in aptitude TUI (coming from Packages files), I think my initial concern was correct.
[..]
I'm not seeing how it is feasible for the Archive team to properly handle the overrides, when they no longer have custody of the NEW processing, which is where overrides were applied.
[..]
(For context, long ago, the Section value determined how packages would be organized in the archive file hierarchy, before pools were introduced. Priority values have an effect of how bootstrap tools select which packages to install. But any field can be overridden, as in changed, added or removed, see for example the injected Build-Essential field.)
I'm wondering for the longest time if overriding the section and priority "by default" is still useful. Maybe it would nowadays be better to stop overriding section/priority completely (and thus just using the values from the package control files).
I imagine this would reduce the overrides by 99%, leaving only the few actual special cases. These would not need "after the fact fixes", as ISTM they would by definition be "after NEW processing".
Chris
