Jump to: navigation, search


3 bytes removed, 5 months ago
Portage Limitations (Technical)
There is no trivial solution to this that I am aware, but there are potential solutions:
1. # Deprecate {{c|RUBY_TARGETS}}, and have the OS Ruby settings set in the eclass. Now they are defined in one place. This means that users can't override them in {{c|/etc/make.conf}}. The eclasses must live in core-kit for technical reasons, and thus couldn't change automatically if a user changed their Ruby kit. So there are some downsides to this.2. # Deprecate md5-caching, or at least Funtoo-generated cache entries for improved performance. Then a user's local profile settings could be factored in to the md5-cache calculation. This would allow eclasses to interact with dynamic profile settings. It could reduce speed of Portage temporarily since it would need to rebuild its cache more often. If cache regen were fast enough, this wouldn't matter (and Funtoo has much faster cache regeneration code than Gentoo which could be leveraged.)3. # Just deal with the current situation for now, which is at least an improvement. Users don't generally need access to different ruby-kits, except developers when testing, and we have tools for developers to deal with this easily anyway ({{c|merge-kits}}).
[[Category:Official Documentation]]
Bureaucrats, Administrators, wiki-admins, wiki-staff

Navigation menu