Richard Fish wrote:
Having dozens (hundreds? all?) ebuilds check for a minimum version
Probably just the ebuilds that happen to use new GCC features before the mass of the general public has changed to that version. But yes, a minimum version constraint could theoretically end up in a lot of packages.
of gcc doesn't seem very effecient.
I can't see why it would not be efficient?
I don't think the issue is as simple as either having xine-lib put out a warning about a particular gcc version, as that doesn't work in the general case.
Obviously any solution implemented should work for all ebuilds, not just xine-lib.
And putting the checks in portage doesn't seem to work very well either.
I fail to see how a test in the ebuild for the active GCC compiler version wouldn't work?
The system as it is now actually seems to work about right... the vast majority of stable users upgrade to new versions of gcc as they come out
Really? How do you gather? I'd think that most users hadn't even run into this problem (yet), because many source code maintainers strive to be able to compile with as old a version of GCC as possible.. -- [email protected] mailing list
