public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Need clear semantics for packages with binary entities
Date: Wed, 30 Dec 2015 08:28:23 -0800	[thread overview]
Message-ID: <56840627.9090003@gentoo.org> (raw)
In-Reply-To: <20151228182414.GB4303@web>

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


  parent reply	other threads:[~2015-12-30 16:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-28 18:24 [gentoo-dev] Need clear semantics for packages with binary entities trupanka
2015-12-28 18:33 ` Michał Górny
2015-12-30 12:13   ` Kristian Fiskerstrand
2015-12-30 16:28 ` Zac Medico [this message]
2015-12-31  0:14 ` Chí-Thanh Christopher Nguyễn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56840627.9090003@gentoo.org \
    --to=zmedico@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox