Summary: | ruby-ng.eclass: eclass should not alter or limit dependencies defined by ebuild | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Gordon Bos <bugzilla> |
Component: | Eclasses | Assignee: | Gentoo Ruby Team <ruby> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | leio, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Gordon Bos
2018-05-04 14:00:20 UTC
While this issue is in fact more of a general issue, it seems to me that as this is being treated as a ruby specific issue and connected to ruby 2.2 there is no point in pursuing this and we can mark this as obsolete. To stipulate the original issue, as a device specific OS maintainer I find fairly frequent frustration in eclasses overriding system forced constraints and/or enforcing stricter requirements for no apparent reason, causing conflicts that a regular user will have a hard time solving when attempting world updates. As I understand eclasses fall under the responsibility of the various maintainer groups, however as these are also part of the portage tree I feel that there should be better communication between you and the portage maintainer group to prevent breakage on systems other than the most common amd64. (In reply to Gordon Bos from comment #1) > While this issue is in fact more of a general issue, it seems to me that as > this is being treated as a ruby specific issue and connected to ruby 2.2 > there is no point in pursuing this and we can mark this as obsolete. > > To stipulate the original issue, as a device specific OS maintainer I find > fairly frequent frustration in eclasses overriding system forced constraints > and/or enforcing stricter requirements for no apparent reason, causing > conflicts that a regular user will have a hard time solving when attempting > world updates. In general, if you feel there's a pointless change, you're free to ask us about it. But the Ruby eclasses in particular handle this differently to the rest of the ecosystem like Python and Lua. Help would be welcome in maintaining things and input from a different perspective if you're willing to help with the upkeep of older stuff anyway. |