I don't think we have a valid use case for this RESTRICT. Devmanual tries hard to come up with something: | this is sometimes useful if approximate download counts are needed, | or if upstream have a reliable mirror setup. The first argument is silly -- for redistributable stuff, downloads counts are meaningless. The second contradicts what it says earlier -- if stuff gets distributed to Gentoo mirrors, there's no reason not to use them. We have exactly three packages using this right now. I've filed bugs for all of them to learn why the maintainers enabled it.
PMS doesn't mention this, therefore removing pms@ from CC.
Ok, there's a last consumer left, devmanual has been updated and nobody brought any new argument why this is necessary. Therefore I'd like to call a vote. Vote: ban RESTRICT=primaryuri in ::gentoo (removed it from allowed RESTRICT list)
I vote yes.
Do we even have to vote on this? As I said in comment #1, primaryuri is not mentioned by the spec, so ebuilds cannot rely on its being supported. (In case we do, I vote yes.)
yes
aye
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c74fb98c07aa4bf07dfc3974de5549b3a28cf3ca commit c74fb98c07aa4bf07dfc3974de5549b3a28cf3ca Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2019-11-02 11:43:02 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2019-11-02 11:43:02 +0000 metadata/layout.conf: Disallow RESTRICT=primaryuri Bug: https://bugs.gentoo.org/696832 Signed-off-by: Michał Górny <mgorny@gentoo.org> metadata/layout.conf | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
Never used it, did not know that it was a thing... So, yes from me too, if it matters...
