Simon Stelling wrote: > Carsten Lohrke wrote: >> One question remains: Is it needed/correct that Portage doesn't take >> blockers >> for architecture breakages into account? Such a line/prefix is easily >> changed >> and when someone - whatever the bad reason is - uses cvs commit, a real tree >> breakage is the cause. > > The behaviour is correct. The depstring in question was > "!<app-text/hunspell-1.0", which means that you can't have <hunspell-1.0 > and kdelibs installed on a system at the same time. Reason for this > could e.g. be file collisions that got fixed in hunspell-1.0. > > If the depstring was "!<app-text/hunspell-1.0 app-text/hunspell", (same > as ">=app-text/hunspell-1.0", just retarded) repoman would complain loudly.
Well, now the ebuild is broken even worse, since the blocker is gone [1] and hspell is still not disabled, so it will go kaboom when someone installs the stable version. [1] http://sources.gentoo.org/viewcvs.py/gentoo-x86/kde-base/kdelibs/kdelibs-3.5.4-r1.ebuild?r1=1.4&r2=1.5 carlo, you might want to revert it properly, instead of reverting only half of the previous commit you've been complaining about here. -- 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
