| Summary: | Make eclass functions more strict | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Marat Radchenko <marat> |
| Component: | [OLD] Java | Assignee: | Java team <java> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | alex_y_xu |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Marat Radchenko
2007-04-28 12:57:32 UTC
The problem with some of these functions is that they are typically called from a subshell, ie: eant -Dsomejar=$(java-pkg_getjar something) As a result, having it die wouldn't get you anything, since it would die in the subshell. (In reply to comment #0) > eant doesn't die if it cannot find package for specified ANT_TASKS. Hm that would be ant script itself, not eant function. You're probably right it should do that now. (In reply to comment #1) > As a result, having it die wouldn't get you anything, since it would die in the > subshell. I remember some notice on -dev about die in subshell now somewhat working, although not 100% reliably :/ most java ebuilds appear to die, closing. |
