View previous topic :: View next topic |
Author |
Message |
Colt45 Tux's lil' helper
Joined: 05 Sep 2007 Posts: 123 Location: Central Washington
|
Posted: Fri Feb 07, 2025 11:02 pm Post subject: GCC and Python timelines |
|
|
Is there a place which shows what the anticipated dates are for things like GCC and python that are critical to the system
For example, Python 3.13 is the current fully supported version.
3.10, 11 and 12 are still available.
When is 10 getting dropped from Gentoo and anyone still on it will have to upgrade?
I ask because Ive begun holding back systems from latest stable due to too many build issues even though they are supposedly stable.
Ive done the same with gcc now too. gcc-14 imo was pushed out too early. I moved to it and then ended up doing a -eav world as part of the update to 23.0 profile and kept encountering packages that wouldnt build. Finally it got to a package I couldnt just skip and I ended up rolling it back to 13 and starting the -eav world all over again as I couldnt find a replacement or fix for that package. So now Im just sticking with 13 on all my machines. How long will I have before I need to upgrade realistically?
Thanks, |
|
Back to top |
|
|
ian.au l33t
Joined: 07 Apr 2011 Posts: 610 Location: Australia
|
Posted: Sat Feb 08, 2025 12:02 am Post subject: |
|
|
Colt45
Quote: | Is there a place which shows what the anticipated dates are for things like GCC and python that are critical to the system
For example, Python 3.13 is the current fully supported version.
3.10, 11 and 12 are still available. |
On my stable systems 3:10 hasn't been pulled-in since March 2023. The fact it's supported isn't really relevant.
I can't think of a good reason to keep Python back from stable on gentoo, it's best to go with the dev's on this.
Why not list the packages that you believe require the older version(s) and helpers can perhaps work out why you have problems updating. I haven't really had any trouble (not of my own making) with python or gcc for years.
You know, emerge info, some failed build logs etc.
That may be more helpful in the long run than sweating on upgrades and/or keeping personal overlays for probably unnecessary work-arounds.
All this comes from upstream anyway, then stabilised as required in portage, for gcc ie.
https://gcc.gnu.org/develop.html#timeline |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|