| 1 |
On Sun, 03 Nov 2013 10:53:13 +0200 |
| 2 |
Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
| 3 |
|
| 4 |
> On 02/11/2013 17:03, Michał Górny wrote: |
| 5 |
> Sadly, it's somewhat common for (newish) users to not know what to do |
| 6 |
> with that. Blocker output can be quite daunting in the beginning, |
| 7 |
> especially if it's in the middle of 20 other things portage is also |
| 8 |
> updating. |
| 9 |
|
| 10 |
+1 I agree, we should look into having errors not only tell what we |
| 11 |
should not do, but also tell what we could do; every time I see a |
| 12 |
blocker it is annoying that I have to go manually search the solution. |
| 13 |
|
| 14 |
Let's say I have the blocker: |
| 15 |
|
| 16 |
<dev-python/python-exec-10000 is blocking |
| 17 |
dev-lang/python-exec-0.3.1 |
| 18 |
|
| 19 |
We could have it additionally say something like: |
| 20 |
|
| 21 |
To resolve this blocker, you can run one of the following commands: |
| 22 |
|
| 23 |
emerge -1 '>=dev-python/python-exec-10000' |
| 24 |
|
| 25 |
Taking another example: |
| 26 |
|
| 27 |
<dev-lang/vala-0.20.0" is blocking |
| 28 |
dev-libs/gobject-introspection-1.36.0-r1 |
| 29 |
|
| 30 |
Why not have it say: |
| 31 |
|
| 32 |
To resolve this blocker, you can run one of the following commands: |
| 33 |
|
| 34 |
emerge -1 '>=dev-lang/vala-0.20.0' |
| 35 |
emerge -1 '<dev-libs/gobject-introspection-1.36.0' |
| 36 |
|
| 37 |
For the last example it was smart enough to see 1.36.0 and 1.36.0-r1 |
| 38 |
have this blocker, whereas the lower versions did not; and if there's a |
| 39 |
range, it could just list all options. |
| 40 |
|
| 41 |
This spares me out from having to inspect "${PORTDIR}"/dev-lang/vala |
| 42 |
and "${PORTDIR}"/dev-libs/gobject-introspection manually to figure out |
| 43 |
what's really going on; it's quite repetitive work that we currently |
| 44 |
need to do manually for every blocker we meet, which can be automated. |
| 45 |
|
| 46 |
Do other people like this idea? Should it be worded differently? If so, |
| 47 |
I might try to work out a patch together with the Portage team. |
| 48 |
|
| 49 |
!! Moving this sub discussion to the Portage Dev ML; please respond |
| 50 |
there and drop gentoo-dev from CC, thank you very much in advance. |
| 51 |
|
| 52 |
-- |
| 53 |
With kind regards, |
| 54 |
|
| 55 |
Tom Wijsman (TomWij) |
| 56 |
Gentoo Developer |
| 57 |
|
| 58 |
E-mail address : TomWij@g.o |
| 59 |
GPG Public Key : 6D34E57D |
| 60 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |
Archives