Summary: | app-eselect/eselect-ruby should check RUBY_TARGETS | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Hans de Graaff <graaff> |
Component: | Current packages | Assignee: | Gentoo Ruby Team <ruby> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | esigra, gentoo, pacho, patrick, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Hans de Graaff
![]() ![]() I'm in favor of option 2). Maybe we can add some pkg_postinst message, via our ruby eclasses, that notifies the user about this issue. Where is RUBY_TARGETS set, if there is not a setting in /etc/make.conf? (In reply to Manuel Rüger from comment #1) > I'm in favor of option 2). > Maybe we can add some pkg_postinst message, via our ruby eclasses, that > notifies the user about this issue. profiles/base/make.defaults I thought about something like that: all_ruby_fakegem_pkg-postinst() { if [[ ${RUBY_TARGETS} =~ .*${RUBY}.* ]]; then ewarn "Your currently eselected ruby is not included in your current RUBY_TARGETS" fi } *** Bug 485158 has been marked as a duplicate of this bug. *** *** Bug 484278 has been marked as a duplicate of this bug. *** |