Brian,

I was looking through /usr/bin/emerge and lines 3477-3481 seemed to
best fit what displayConfirmPrompt is trying to supplement. The check
on line 3477 is against a "No" returned from userPrompt(), and then a
system exit code is issued by caller (line 3481).

Was unable to find any other instance of the function being called
issuing a system code in the emerge code, could you please point me in
the direction you wanted me to go with this?

On 7/20/06, Brian Harring <[EMAIL PROTECTED]> wrote:

Examples of converted ebuilds would be wise prior to plopping it into
the tree imo- fex, displayConfirmPrompt looks like it should be
reliant on exit codes rather then mangling a global var to indicate
the outcome; that would shift it more towards "get confirmation"
rather then display.


Thank you for the kudos Doug.

On 7/20/06, Doug Goldstein <[EMAIL PROTECTED]> wrote:
John,

I think you've done a really great job with this. Very creative and good
initiative. You're hired. Someone get him his developer badge..

Regards,
John
"Open source, you don't pay back, you pay forward."
--
gentoo-dev@gentoo.org mailing list

Reply via email to