From: Peter Hjalmarsson <xake@rymdraket.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Packages pulling in python-3*, also they dont require it
Date: Sat, 20 Mar 2010 13:47:20 +0100 [thread overview]
Message-ID: <1269089240.15822.6.camel@lillen> (raw)
In-Reply-To: <4BA34E5C.7040800@gmail.com>
fre 2010-03-19 klockan 05:13 -0500 skrev Dale:
> Because, when I installed gcc 4.3, I could then unmerge the old gcc.
> That's why I didn't complain about that. With python, we still have to
> have the current version plus the new version which is not being used at
> all.
>
That was if you did not use qemu that did *not* compile or run with a
gcc never then gcc-3 for a couple of years...
Also search for "gcc-porting" in b.g.o and guess what: there are many
packages that fits this description for gcc, qemu was just a special
case since for it it actually took YEARS before upstream released a
version that worked with gcc-4, most other packages is often easier to
patch (since it is mostly compile-time brokenness related to headers or
other "small" fixes) and our awesome toolchain guys helps fixing it up
before it hits ~arch.
next prev parent reply other threads:[~2010-03-20 12:47 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 19:20 [gentoo-dev] Packages pulling in python-3*, also they dont require it Thomas Sachau
2010-03-18 19:24 ` Fabian Groffen
2010-03-18 20:27 ` Ben de Groot
2010-03-18 20:53 ` Doktor Notor
2010-03-18 22:09 ` Sebastian Pipping
2010-03-18 22:17 ` Ben de Groot
2010-03-19 8:12 ` Ciaran McCreesh
2010-03-19 8:54 ` Dale
2010-03-19 8:57 ` Ciaran McCreesh
2010-03-19 9:23 ` Dale
2010-03-19 9:30 ` Ciaran McCreesh
2010-03-19 10:13 ` Dale
2010-03-19 10:34 ` Arfrever Frehtes Taifersar Arahesis
2010-03-19 14:54 ` Dale
2010-03-20 0:51 ` [gentoo-dev] " Duncan
2010-03-20 9:56 ` Jean-Marc Hengen
2010-03-20 12:53 ` Zac Medico
2010-03-20 14:11 ` Arfrever Frehtes Taifersar Arahesis
2010-03-22 21:12 ` Jacob Godserv
2010-03-23 15:37 ` Arfrever Frehtes Taifersar Arahesis
2010-03-23 16:15 ` Duncan
2010-03-20 12:47 ` Peter Hjalmarsson [this message]
2010-03-19 9:35 ` [gentoo-dev] " Arfrever Frehtes Taifersar Arahesis
2010-03-19 9:39 ` Petteri Räty
2010-03-19 9:55 ` Arfrever Frehtes Taifersar Arahesis
2010-03-19 9:56 ` Brian Harring
2010-03-19 10:01 ` Ciaran McCreesh
2010-03-19 10:27 ` Brian Harring
2010-03-19 9:40 ` Brian Harring
2010-03-19 15:13 ` [gentoo-dev] " Nikos Chantziaras
2010-03-19 18:26 ` Alec Warner
2010-03-20 12:42 ` Nikos Chantziaras
2010-03-19 5:35 ` [gentoo-dev] " Alec Warner
2010-03-19 7:15 ` Dale
2010-03-19 7:58 ` Zac Medico
2010-03-19 8:52 ` Dale
2010-03-19 9:09 ` Zac Medico
2010-03-19 22:28 ` Alistair Bush
2010-03-19 15:02 ` Dale
2010-03-19 15:21 ` Doktor Notor
2010-03-18 19:28 ` Ciaran McCreesh
2010-03-18 19:43 ` Thomas Sachau
2010-03-18 20:02 ` Petteri Räty
2010-03-18 20:10 ` Ciaran McCreesh
2010-03-18 20:57 ` Petteri Räty
2010-03-18 20:21 ` Thomas Sachau
2010-03-18 21:00 ` Petteri Räty
2010-03-18 21:06 ` Ciaran McCreesh
2010-03-18 21:45 ` Thomas Sachau
2010-03-18 19:33 ` Arfrever Frehtes Taifersar Arahesis
2010-03-18 19:47 ` Thomas Sachau
2010-03-18 19:55 ` Arfrever Frehtes Taifersar Arahesis
2010-03-18 20:13 ` Thomas Sachau
2010-03-18 21:40 ` Brian Harring
2010-03-20 12:51 ` [gentoo-dev] " Peter Hjalmarsson
2010-03-20 14:07 ` Arfrever Frehtes Taifersar Arahesis
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=1269089240.15822.6.camel@lillen \
--to=xake@rymdraket.net \
--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