From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id B90411384B4 for ; Wed, 30 Dec 2015 16:28:42 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 107D921C0FB; Wed, 30 Dec 2015 16:28:27 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 2DD4321C021 for ; Wed, 30 Dec 2015 16:28:26 +0000 (UTC) Received: from [192.168.0.16] (ip174-67-193-3.oc.oc.cox.net [174.67.193.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: zmedico) by smtp.gentoo.org (Postfix) with ESMTPSA id 1DA68340756 for ; Wed, 30 Dec 2015 16:28:25 +0000 (UTC) Subject: Re: [gentoo-dev] Need clear semantics for packages with binary entities To: gentoo-dev@lists.gentoo.org References: <20151228182414.GB4303@web> From: Zac Medico X-Enigmail-Draft-Status: N1110 Message-ID: <56840627.9090003@gentoo.org> Date: Wed, 30 Dec 2015 08:28:23 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 In-Reply-To: <20151228182414.GB4303@web> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Archives-Salt: 962459fa-2cc9-45e1-b6a8-e45543aa78ae X-Archives-Hash: 2b096a8d291d1bab8ec8a365bc1874b8 On 12/28/2015 10:24 AM, trupanka@gmail.com wrote: > I’m suffering from the fact that users can distinguish packages containing > binaries just by eye. There is no mechanism to allow/ignore such packages. > For license restrictions we have ‘package.license/’ whitelist. We can use the PROPERTIES variable (or alternatively the RESTRICT variable) to tag this information in the ebuild. Portage has a ACCEPT_PROPERTIES configuration variable, and a package.properties file that can be used to mask and unmask packages based on PROPERTIES. It would be useful to be able to do this with "live" ebuilds too... -- Thanks, Zac