From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org,
Arfrever Frehtes Taifersar Arahesis <Arfrever@gentoo.org>
Cc: Gentoo Council <council@gentoo.org>
Subject: Re: [gentoo-dev] Extending EAPI="4"
Date: Fri, 19 Nov 2010 07:51:03 -0800 [thread overview]
Message-ID: <4CE69CE7.6040907@gentoo.org> (raw)
In-Reply-To: <201010251524.24984.Arfrever@gentoo.org>
On 10/25/2010 06:24 AM, Arfrever Frehtes Taifersar Arahesis wrote:
> use.unsatisfiable and package.use.unsatisfiable files would cause that `repoman` would treat
> given USE flags in the same way as masked USE flags. These files wouldn't affect behavior of
> `emerge`:
> - If user has enabled given USE flag specified in use.unsatisfiable or package.use.unsatisfiable
> and if optional dependencies controlled by this USE flag are already installed or satisfiable,
> then `emerge` will allow to install given package.
> - If user has enabled given USE flag specified in use.unsatisfiable or package.use.unsatisfiable
> and if optional dependencies controlled by this USE flag cannot be satisfied (with current
> settings of ACCEPT_KEYWORDS, /etc/portage/package.keywords etc.), then `emerge` will print
> informative error message telling e.g. about a dependency masked by ~${ARCH} keyword.
Can't we print a "masked by ~${ARCH} keyword" message as you suggest,
even without the use.unsatisfiable data? If so, then isn't
use.unsatisfiable redundant? Your patch [1] seems to behave exactly like
use.mask, so I don't see any value added.
As an alternative, I'd suggest an atom syntax extension to indicate that
a given atom is optional. For example, we could borrow the '?' character
from regular expression syntax, and append '?' to the right side of an
atom in order to indicate that it is an optional atom.
[1]
http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=93ee6a847be949e7752c3c052d3eb0619e408b43
--
Thanks,
Zac
next prev parent reply other threads:[~2010-11-19 15:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 13:24 [gentoo-dev] Extending EAPI="4" Arfrever Frehtes Taifersar Arahesis
2010-10-25 13:42 ` Ciaran McCreesh
2010-10-25 13:56 ` Arfrever Frehtes Taifersar Arahesis
2010-10-25 14:03 ` Ciaran McCreesh
2010-10-25 15:03 ` Arfrever Frehtes Taifersar Arahesis
2010-11-15 20:17 ` Arfrever Frehtes Taifersar Arahesis
2010-10-25 13:56 ` Ulrich Mueller
2010-10-25 14:03 ` Ciaran McCreesh
2010-10-25 14:05 ` Arfrever Frehtes Taifersar Arahesis
2010-10-25 14:43 ` Fabio Erculiani
2010-10-25 15:00 ` Arfrever Frehtes Taifersar Arahesis
2010-10-25 16:12 ` Thomas Sachau
2010-10-25 16:23 ` Petteri Räty
2010-10-25 16:32 ` Diego Elio Pettenò
2010-10-25 16:44 ` Matti Bickel
2010-11-19 15:51 ` Zac Medico [this message]
2010-11-28 18:15 ` Arfrever Frehtes Taifersar Arahesis
2010-11-28 19:59 ` Zac Medico
2010-11-28 20:07 ` Arfrever Frehtes Taifersar Arahesis
2010-11-28 20:30 ` Zac Medico
2010-11-28 21:56 ` Arfrever Frehtes Taifersar Arahesis
2010-11-28 22:06 ` Zac Medico
2010-11-28 22:07 ` Petteri Räty
-- strict thread matches above, loose matches on Subject: below --
2010-06-06 13:52 Arfrever Frehtes Taifersar Arahesis
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=4CE69CE7.6040907@gentoo.org \
--to=zmedico@gentoo.org \
--cc=Arfrever@gentoo.org \
--cc=council@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