| 1 |
On Mon, Nov 28, 2005 at 05:24:52PM -0500, Daniel Gryniewicz wrote: |
| 2 |
> On Mon, 2005-11-28 at 19:12 +0100, Bjarke Istrup Pedersen wrote: |
| 3 |
> > Does this mean that we can get rid of the libstd++ dependency of gcc, |
| 4 |
> > and move it to the binary packages that depends on gcc 3.3 . |
| 5 |
> > I know this has been discussed before, but once it's stable I see no |
| 6 |
> > reason to keep the dependency in the gcc ebuild, when it could be in the |
| 7 |
> > binary packages. |
| 8 |
> |
| 9 |
> Well, right after the upgrade, there will still be tons of non-binary |
| 10 |
> programs built against the old libstdc++, so no. Unless you want to |
| 11 |
> force everyone to emerge -e world after the upgrade (which will make you |
| 12 |
> very unpopular). |
| 13 |
|
| 14 |
not really an issue ... gcc is SLOTed for everyone to gccmajor.gccminor |
| 15 |
|
| 16 |
that means when people upgrade to gcc-3.4, gcc-3.3 will remain on their |
| 17 |
system until they remove it |
| 18 |
|
| 19 |
so if user fails to rebuild all their packages before unmerging gcc-3.3 |
| 20 |
they will be screwed, but OH WELL |
| 21 |
-mike |
| 22 |
-- |
| 23 |
gentoo-dev@g.o mailing list |
Archives