public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] What happened to gcc-12.3.0?
Date: Thu, 15 Jun 2023 17:09:11 +0200	[thread overview]
Message-ID: <5365037.iZASKD2KPV@noumea> (raw)
In-Reply-To: <d69a4f2c-e0ed-f09c-d9d5-edfa0e8098de@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 745 bytes --]

Am Donnerstag, 15. Juni 2023, 06:02:14 CEST schrieb Joshua Kinard:
> 
> Noticing that the ebuild for gcc-12.3.0 got dropped with little explanation.  It is the upstream stable 
> release.  I am eyeballing #906310 as what may have triggered the drop, but I find it a bit of a stretch ...

This is for exactly the same reason as why we don't have glibc-2.36(-r0) or 2.37(-r0) in the tree anymore.
There's a stable upstream branch which accumulates bug and security fixes. The only real difference is 
naming, but I could switch to glibc-2.36_p20230615 too...


-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer 
(council, comrel, toolchain, base-system, perl, libreoffice)
https://wiki.gentoo.org/wiki/User:Dilfridge

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2023-06-15 15:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-15  4:02 [gentoo-dev] What happened to gcc-12.3.0? Joshua Kinard
2023-06-15  5:04 ` Matt Turner
2023-06-15 15:47   ` Joshua Kinard
2023-06-15 11:37 ` Sam James
2023-06-15 16:29   ` Joshua Kinard
2023-06-15 15:09 ` Andreas K. Huettel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5365037.iZASKD2KPV@noumea \
    --to=dilfridge@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox