From: Marc Schiffbauer <mschiff@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] <>-DEPENDS
Date: Mon, 7 Sep 2015 17:31:51 +0200 [thread overview]
Message-ID: <20150907153151.GG14168@schiffbauer.net> (raw)
In-Reply-To: <21B94859-E033-4243-94C3-0433EE041507@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
* Ian Stakenvicius schrieb am 07.09.15 um 16:41 Uhr:
> Why not just:
>
> DEPEND="
> dev-python/paramiko
> !~dev-python/paramiko-1.13.0
> "
>
> Depend on the package but block the individual atom(s) that don't work?
I like it. At least with the current possibilities. I was not aware that
"!~" is already a valid blocker.
>
> Given that there will be *very few* valid use cases for this type of
> syntax I don't know if it's such a good idea to add it. I expect
> adding this new syntax would be more likely to cause issues via
> improper usage than it would add a benefit or fill any massively
> pressing need...
Depending on how it is implemented, I think it would be intuitive to
use. I'd find having "=" vs. "!=" and "~" vs. "!~" straight forward.
You are of cource right that there is no "massively pressing need" atm.
But that was not always a reason for a new feature ;)
-Marc
--
0x35A64134 - 8AAC 5F46 83B4 DB70 8317
3723 296C 6CCA 35A6 4134
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2015-09-07 15:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 12:35 [gentoo-dev] <>-DEPENDS Marc Schiffbauer
2015-09-07 12:58 ` Jauhien Piatlicki
2015-09-07 13:07 ` Ulrich Mueller
2015-09-07 15:20 ` Marc Schiffbauer
2015-09-07 13:18 ` Kent Fredric
2015-09-07 15:26 ` Marc Schiffbauer
2015-09-08 4:58 ` Kent Fredric
2015-09-07 14:41 ` Ian Stakenvicius
2015-09-07 15:31 ` Marc Schiffbauer [this message]
2015-09-07 15:16 ` Michał Górny
2015-09-07 15:58 ` Marc Schiffbauer
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=20150907153151.GG14168@schiffbauer.net \
--to=mschiff@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