| Summary: | packages using gems.eclass will succeed even when gem install fails with rubygems-1.0.1 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Josh Nichols (RETIRED) <nichoj> |
| Component: | New packages | Assignee: | Gentoo Ruby Team <ruby> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | gentoo-bugzilla |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://rubyforge.org/tracker/index.php?func=detail&aid=17438&group_id=126&atid=575 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | work around the missing exit status until rubygems is fixed | ||
Created attachment 143775 [details, diff]
work around the missing exit status until rubygems is fixed
This patch implements a work-around until rubygems is fixed. I'm probably not the world's best bash programmer, so comments are welcome!
Closing this bug since dev-ruby/rubygems-1.0.1 is no longer in the tree, and this got fixed upstream, and consequently is fixed in all versions currently in the tree. Josh, thanks for reporting it there. |
There's a bug in rubygems-1.0.1 that doesn't set the proper exitcode on failure, so the line in gems.eclass: gem install ${GEM_SRC} --version ${PV} ${myconf} \ --local --install-dir "${D}/${GEMSDIR}" || die "gem install failed" the die never gets called. Filed an upstream bug at http://rubyforge.org/tracker/index.php?func=detail&aid=17438&group_id=126&atid=575