| 1 |
Simon Stelling wrote: |
| 2 |
> Carsten Lohrke wrote: |
| 3 |
>> One question remains: Is it needed/correct that Portage doesn't take blockers |
| 4 |
>> for architecture breakages into account? Such a line/prefix is easily changed |
| 5 |
>> and when someone - whatever the bad reason is - uses cvs commit, a real tree |
| 6 |
>> breakage is the cause. |
| 7 |
> |
| 8 |
> The behaviour is correct. The depstring in question was |
| 9 |
> "!<app-text/hunspell-1.0", which means that you can't have <hunspell-1.0 |
| 10 |
> and kdelibs installed on a system at the same time. Reason for this |
| 11 |
> could e.g. be file collisions that got fixed in hunspell-1.0. |
| 12 |
> |
| 13 |
> If the depstring was "!<app-text/hunspell-1.0 app-text/hunspell", (same |
| 14 |
> as ">=app-text/hunspell-1.0", just retarded) repoman would complain loudly. |
| 15 |
|
| 16 |
Well, now the ebuild is broken even worse, since the blocker is gone [1] |
| 17 |
and hspell is still not disabled, so it will go kaboom when someone |
| 18 |
installs the stable version. |
| 19 |
|
| 20 |
[1] |
| 21 |
http://sources.gentoo.org/viewcvs.py/gentoo-x86/kde-base/kdelibs/kdelibs-3.5.4-r1.ebuild?r1=1.4&r2=1.5 |
| 22 |
|
| 23 |
carlo, you might want to revert it properly, instead of reverting only |
| 24 |
half of the previous commit you've been complaining about here. |
| 25 |
|
| 26 |
-- |
| 27 |
Best regards, |
| 28 |
|
| 29 |
Jakub Moc |
| 30 |
mailto:jakub@g.o |
| 31 |
GPG signature: |
| 32 |
http://subkeys.pgp.net:11371/pks/lookup?op=get&search=0xCEBA3D9E |
| 33 |
Primary key fingerprint: D2D7 933C 9BA1 C95B 2C95 B30F 8717 D5FD CEBA 3D9E |
| 34 |
|
| 35 |
... still no signature ;) |
Archives