Summary: | webapp-config doesn't play nice with IO (--ask in EMERGE_DEFAULT_OPTS) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michael Stewart (vericgar) (RETIRED) <vericgar> |
Component: | Current packages | Assignee: | Gentoo Web Application Packages Maintainers <web-apps> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 124440 | ||
Bug Blocks: |
Description
Michael Stewart (vericgar) (RETIRED)
2006-03-21 20:49:16 UTC
*** This bug has been marked as a duplicate of 124440 *** I do not believe this is a duplicate bug. webapp-config is a seperate application from the eclass. Unless the application itself is not going to call emerge, then this issue will not be fixed by removing the emerge calls from the eclass. Hm, webapp-config never directly calls emerge. It imports portage though. It does that in order to access portage.settings. I don't see how that could trigger --ask. The webapp.eclass on the other hand contains a direct "emerge" call that we still need to replace. The portage version I have currently installed (2.0.54) does not provide the EMERGE_DEFAULT_OPTS feature. So I guess I should upgrade to unstable for a test. Which version features this new variable? Can you give an example under which conditions webapp-config hangs? Does it hang while you install/clean/upgrade and does it provide any output before it stalls? vericgar, please reply to comment #3, thanks. |