Bug 542480

Summary:	sys-apps/portage: Add an option or a configuration variable to suppress building of binpkgs (e.g. for bindist restricted ebuilds)
Product:	Portage Development	Reporter:	Ulrich Müller <ulm>
Component:	Binary packages support	Assignee:	Portage team <dev-portage>
Status:	CONFIRMED ---
Severity:	enhancement	CC:	binhost, dilfridge, sam
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	All
See Also:	https://bugs.gentoo.org/show_bug.cgi?id=885827 https://bugs.gentoo.org/show_bug.cgi?id=911825
Whiteboard:
Package list:		Runtime testing required:	---

Description Ulrich Müller gentoo-dev

2015-03-07 21:23:56 UTC

Currently, it is only possible to mask bindist restricted ebuilds completely, by setting -bindist in ACCEPT_RESTRICT or --accept-restrict.

It would be nice if there was an option and/or variable that would suppress only building of binary packages for bindist restricted ebuilds, but otherwise not influence installation.

Comment 1 Andreas K. Hüttel archtester

2024-04-12 09:46:30 UTC

We could always introduce RESTRICT=binpkg , which, if used in an ebuild, forbids the generation of a binary package.

Comment 2 Ulrich Müller gentoo-dev

2024-04-12 10:18:21 UTC

(In reply to Andreas K. Hüttel from comment #1)
> We could always introduce RESTRICT=binpkg , which, if used in an ebuild,
> forbids the generation of a binary package.

Sorry, but I see little use for such a restriction at the ebuild level. How would it be differenciated against "bindist" restriction, which exists mostly for license reasons?

Whether binpkgs should be built for bindist-restricted ebuilds seems to fit better with user preferences like FEATURES or an emerge options.