Summary: | Some ebuilds install precompiled binaries, without there being any way to prevent their installation | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Elliot Chandler <elliot> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | major | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Elliot Chandler
2016-10-24 20:01:08 UTC
I am not aware of any existing Gentoo packaging policy requiring that ebuilds must compile things from source code. Sometimes it just isn't practical. Being able to more easily identify "binary" ebuilds seems like a nice idea, but bugzilla is not the discussion forum for it. There was a recent discussion thread on the gentoo-dev mailing list where you might voice your concerns or help come up with a solution. The clarify: if you can come up with some specific changes that would improve things, we can route enhancement requests to the Portage or PMS maintainers. But a generic rant about binary ebuilds is not actionable. The mailing list discussion on this issue is at https://archives.gentoo.org/gentoo-dev/message/ecc121d7e1e74cb108034296fcf44818 In that thread, solutions of adding a metadata entry, or requiring packages to be named with -bin were suggested. In IRC, it was suggested to implement this by adding a value to RESTRICT; in my opinion that is the best solution. In response to further discussion on IRC, it seems I should send that summary of proposed solutions to the mailing list, to develop consensus on a single one on which to file a bug. Thanks! |