| 1 |
On Thu, 5 Jan 2006 16:08:04 +0000, Tom Martin wrote: |
| 2 |
|
| 3 |
> > if_blocked_by('openmotif') |
| 4 |
> > ewarn "You must unmerge openmotif before proceeding" |
| 5 |
> |
| 6 |
> An error message like that doesn't really tell the user anything that he |
| 7 |
> doesn't already know. |
| 8 |
|
| 9 |
It may not say anything you or I don't know, but from the number of posts |
| 10 |
to this list about blockers, it would clearly help some people. |
| 11 |
|
| 12 |
> It would be more useful if some information was provided: |
| 13 |
> |
| 14 |
> if blocked_by >=x11-libs/openmotif-1.2.3 ; then |
| 15 |
> eblockinfo "Due to changes with blah, it is recommended that" |
| 16 |
> eblockinfo "you foobar. See http://bugs.gentoo.org/123456." |
| 17 |
> fi |
| 18 |
> |
| 19 |
> But then, at what point would this information be echoed to the user? |
| 20 |
> It would have to be during the same pre-merge phase that the blocking |
| 21 |
> errors appear. |
| 22 |
|
| 23 |
Yes, so instead of rushing to this list or the forums, they can do what |
| 24 |
the message tells them and be on their way. The current messages are only |
| 25 |
useful if you already understand how and why blocks happen, and how to |
| 26 |
deal with them. |
| 27 |
|
| 28 |
|
| 29 |
-- |
| 30 |
Neil Bothwick |
| 31 |
|
| 32 |
If you got the words it does not mean you got the knowledge. |
Archives