| 1 |
Brian, |
| 2 |
|
| 3 |
I was looking through /usr/bin/emerge and lines 3477-3481 seemed to |
| 4 |
best fit what displayConfirmPrompt is trying to supplement. The check |
| 5 |
on line 3477 is against a "No" returned from userPrompt(), and then a |
| 6 |
system exit code is issued by caller (line 3481). |
| 7 |
|
| 8 |
Was unable to find any other instance of the function being called |
| 9 |
issuing a system code in the emerge code, could you please point me in |
| 10 |
the direction you wanted me to go with this? |
| 11 |
|
| 12 |
On 7/20/06, Brian Harring <ferringb@×××××.com> wrote: |
| 13 |
> |
| 14 |
> Examples of converted ebuilds would be wise prior to plopping it into |
| 15 |
> the tree imo- fex, displayConfirmPrompt looks like it should be |
| 16 |
> reliant on exit codes rather then mangling a global var to indicate |
| 17 |
> the outcome; that would shift it more towards "get confirmation" |
| 18 |
> rather then display. |
| 19 |
> |
| 20 |
|
| 21 |
Thank you for the kudos Doug. |
| 22 |
|
| 23 |
On 7/20/06, Doug Goldstein <cardoe@g.o> wrote: |
| 24 |
> John, |
| 25 |
> |
| 26 |
> I think you've done a really great job with this. Very creative and good |
| 27 |
> initiative. You're hired. Someone get him his developer badge.. |
| 28 |
|
| 29 |
Regards, |
| 30 |
John |
| 31 |
"Open source, you don't pay back, you pay forward." |
| 32 |
-- |
| 33 |
gentoo-dev@g.o mailing list |
Archives