Molle Bestefich wrote: > I noticed that several users have commented with a relevant complaint: > GCC-4.x is required by the ebuild, but no information is ever conveyed > to the end user about this fact. The ebuild does not have a > dependency on GCC-4.x.
No, it's not. gcc-3.4.x *is* required. That versions (or later) is *stable* everywhere where xine-lib is stable. > Try reading the bug - users are basically being shoved off with an > arrogant silence and a stamp on their forehead saying INVALID. > > Nothing personal against Jakub Moc who probably has a lot to do, but > the handling of relevant issues raised in the bugzilla is just > unacceptable. Dependency on a particular gcc version will solve exactly nothing. Having that version installed doesn't mean you are really *using* it. You won't be automagically switched to 3.4.x when upgrading from 3.3.x, you won't be automatically switched to gcc 4.x when upgrading from 3.4.x http://www.gentoo.org/doc/en/gcc-upgrading.xml > What's the state of Portage and Gentoo in general? Is there not > enough hands to do a proper job? Or is it just that none of the devs > see what's wrong because bugs are wrongly being closed marked > "INVALID" such as the above when they're in fact not? How about the you finally upgrade your outdated gcc, as asked over and over again? gcc-3.3.x is dead, unsupported upstream, we won't be fixing any bugs there. Hard to understand? Apparently, I guess... Thanks for your rant. -- Best regards, Jakub Moc mailto:[EMAIL PROTECTED] GPG signature: http://subkeys.pgp.net:11371/pks/lookup?op=get&search=0xCEBA3D9E Primary key fingerprint: D2D7 933C 9BA1 C95B 2C95 B30F 8717 D5FD CEBA 3D9E ... still no signature ;)
signature.asc
Description: OpenPGP digital signature
