Requested by kensington on request to disable --dynamic-deps by default [1]. Re-quoting for completeness: "The council asks the Portage team to first outline their long-term plan regarding removal or replacement of dynamic dependencies, before they remove this feature. In particular, tree policies and the handling of eclasses and virtuals need to be clarified." Accepted unanimously. The policy has been added to devmanual in September [2,3]. It applies the same to direct changes in ebuilds, and indirect via eclasses (should we explicitly explain that?). However, I don't really know how 'virtuals' come into play here, given that we no longer have old-style virtuals and virtuals are now regular packages. Therefore, I would like to ask Council to state more precisely what needs to be specifically documented before we can stop enabling dynamic-deps in Portage by default. [1]:https://github.com/gentoo/portage/pull/238#issuecomment-352143164 [2]:https://github.com/gentoo/devmanual.gentoo.org/pull/67 [3]:https://devmanual.gentoo.org/general-concepts/ebuild-revisions/index.html
(In reply to Michał Górny from comment #0) > Requested by kensington on request to disable --dynamic-deps by default [1]. > Re-quoting for completeness: > > "The council asks the Portage team to first outline their long-term > plan regarding removal or replacement of dynamic dependencies, > before they remove this feature. In particular, tree policies and > the handling of eclasses and virtuals need to be clarified." > Accepted unanimously. The above was the decision in the 20140826 meeting. I'd like to highlight the following decision in 20151011 summary: ### 3. Runtime dependencies and dynamic dependency deprecation ========================================================== https://archives.gentoo.org/gentoo-project/message/a8b5b499b9dbfdaea57a8f2a158c1fe7 http://article.gmane.org/gmane.linux.gentoo.devel/97742 http://thread.gmane.org/gmane.linux.gentoo.devel/97428/focus=97742 The following policy was accepted by unanimous vote: "Maintainers must not assume that dynamic dependencies will be applied by the package manager. When changing runtime dependencies the maintainer should revision the ebuild if the changes are likely to cause problems for end users." The details, in particular the explicit rules proposed by rich0 on the gentoo-devel mailing list, were referred back to the list for further discussion and should eventually become recommendations. Further decisions on policies may also be up to the QA team. ### > > Therefore, I would like to ask Council to state more precisely what needs to > be specifically documented before we can stop enabling dynamic-deps in > Portage by default. I don't see the need for anything further before the default behavior can be changed in portage, I'm all for it matching PMS behavior.
Merged now, thanks.
