| Summary: | Remove commentary from jarjar ebuild description | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Chris Nokleberg <chris> |
| Component: | [OLD] Development | Assignee: | Java team <java> |
| Status: | RESOLVED FIXED | ||
| Severity: | trivial | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Chris Nokleberg
2005-08-03 10:48:35 UTC
betelgeuse@pena /usr/portage/dev-java/jarjar $ grep DESCRIPTION * ChangeLog: Changed the DESCRIPTION to be neutral. Resolves bug 101231. Thanks to Chris jarjar-0.4_p20050105.ebuild:DESCRIPTION="Tool for repackaging third-party jars." jarjar-0.6.ebuild:DESCRIPTION="Tool for repackaging third-party jars." reopen if the new description is not good and I will change it. Sorry, forgot to mark as fixed and sorry about the trouble in the first place. FYI: The original comment was probably not meant against jarjar itself but the practice of packaging third party jars, which makes life of Gentoo java maintainers hard sometimes. I think you mean "hugely increase java dependency headaches by repackaging third-part jars." Background info: http://gentoo-wiki.com/Gentoo_Java_Policy Well, there aren't too many other solutions when libraries A and B used in the same application depend on incompatible versions of library C. I understand the problem bundled code causes for getting bug fixes propagated, but frankly that's not always the most important consideration. |