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] RFC: masking old versions of sys-devel/gcc
Date: Wed, 26 Apr 2017 11:32:21 +0200	[thread overview]
Message-ID: <33941528.YhSZt8Px0E@pinacolada> (raw)
In-Reply-To: <CAD6zcDwT_HZmUb6TFLSzRxJxxOX+D06V0BuXkXCPTMMciDrmUA@mail.gmail.com>

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

Am Mittwoch, 26. April 2017, 02:37:17 CEST schrieb Francesco Riosa:
> 2017-04-26 0:26 GMT+02:00 Andreas K. Huettel <dilfridge@gentoo.org>:
> > Am Sonntag, 23. April 2017, 14:35:48 CEST schrieb Michał Górny:
> > > Hi,
> > > 
> > > I'm thinking of masking old versions of sys-devel/gcc, in particular
> > > older than the 4.9 branch.
> > 
> > Masking is fine; some time later (maybe in a few months) I'd even suggest
> > masking all of gcc-4. After all, unmasking them if you really need them is
> > rather easy.
> 
> well if the intent is cleaning adding a package mask is just more burden,
> not less.
> If they compile fine with the latest stable gcc better leave them unmasked,
> right?

Except that "switching back" from gcc-5 to gcc-4 doesn't really work, and that 
gcc-4 will happily use gcc-5 libraries, with unintended consequences. 

As far as I understand it, the clean way is to either emerge gcc-5 and set it 
as default, or mask gcc-5 and keep it off your system.

Masking gcc-4 would force people to make a decision.


> > About removing them (what William proposed), I'd keep what we have now. We
> > had
> > this discussion already in lots of detail in the past, and convincing
> > points
> > were made to keep one of each 4.x ...
> 
> do you have any pointers or keyword to search?
> Because once upon a time there were incompatible changes frequently (2.95
> => 3.x with x < 4 was bloody) but nowadays everything "C" seem more stable.
> And the switch to c++11 still ongoing started with 4.8 and far less
> problematic.
> Maybe different arches than amd64? Binary packages? Embedded platforms?

I don't know the details anymore, will search later. But blueness was the 
right person to ask.

-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer (council, perl, libreoffice)

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

  reply	other threads:[~2017-04-26  9:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-23 12:35 [gentoo-dev] RFC: masking old versions of sys-devel/gcc Michał Górny
2017-04-24 16:01 ` William Hubbs
2017-04-24 17:59   ` Guilherme Amadio
2017-04-25 16:26     ` William Hubbs
2017-04-25 16:44       ` Guilherme Amadio
2017-04-25 18:38         ` Francesco Riosa
2017-04-25 22:26 ` Andreas K. Huettel
2017-04-26  0:37   ` Francesco Riosa
2017-04-26  9:32     ` Andreas K. Huettel [this message]
2017-04-26 14:59       ` Mike Gilbert
2017-04-27  2:08       ` Walter Dnes
2017-04-27 15:27   ` William Hubbs
2017-04-27 22:56     ` Andrew Savchenko
2017-04-26  9:42 ` Chí-Thanh Christopher Nguyễn
2017-04-26 12:22   ` Michał Górny

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=33941528.YhSZt8Px0E@pinacolada \
    --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