From: "Paweł Hajdan, Jr." <phajdan.jr@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Request to add ~> atom prefix operator on Portage.
Date: Mon, 14 Sep 2015 20:07:51 +0200 [thread overview]
Message-ID: <55F70CF7.6010507@gentoo.org> (raw)
In-Reply-To: <CAJnmqwYJn=teBS9Q+OBe7Jerx-Y+9hC=_4ioe1g4FX8QvP2v3g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
On 9/14/15 9:13 AM, konsolebox wrote:
> On Mon, Sep 14, 2015 at 2:29 PM, Paweł Hajdan, Jr.
> <phajdan.jr@gentoo.org> wrote:
>> On 9/14/15 6:35 AM, konsolebox wrote:
>>> Many times we need to match packages like this:
>>> something-1.0.2a.*
>>
>> Could you give specific examples, i.e. what packages, what
>> dependencies, why is that needed?
>
> For accuracy and peace of mind regardless of how often conflicts
> could happen.
I agree =pkg-4.1* also matching pkg-4.10 is a concern.
In that case though, it would change the focus of the discussion to how
* operator should work, not necessarily adding a new ~> operator.
I think it'd be okay to e.g. change the meaning and behavior of * in a
new EAPI.
> I can't give any example yet, but we know that if pkg-4.1.2 exists
> and pkg-4.10.0 exists as well, then we can't use '=pkg-4.1*' to only
> target pkg-4.1.*. This could also happen more often with packages
> having 4 version numbers.
It's unfortunate this is rather theoretical now.
Consider looking for some real examples, I believe this could really
help the discussion.
Paweł
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 841 bytes --]
next prev parent reply other threads:[~2015-09-14 18:08 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 4:35 [gentoo-dev] Request to add ~> atom prefix operator on Portage konsolebox
2015-09-14 5:38 ` Daniel Campbell
2015-09-14 6:15 ` konsolebox
2015-09-14 5:47 ` Kent Fredric
2015-09-14 5:51 ` Ulrich Mueller
2015-09-14 6:09 ` konsolebox
2015-09-14 6:19 ` Kent Fredric
2015-09-14 6:43 ` konsolebox
2015-09-14 6:52 ` Ulrich Mueller
2015-09-14 6:59 ` Kent Fredric
2015-09-14 8:01 ` Ulrich Mueller
2015-09-14 8:14 ` Kent Fredric
2015-09-14 9:04 ` Ulrich Mueller
2015-09-14 9:15 ` Kent Fredric
2015-09-14 11:38 ` Ulrich Mueller
2015-09-14 11:45 ` Kent Fredric
2015-09-14 11:53 ` Ulrich Mueller
2015-09-14 9:21 ` Kent Fredric
2015-09-14 11:46 ` Ulrich Mueller
2015-09-14 11:48 ` hasufell
2015-09-14 13:11 ` Ulrich Mueller
2015-09-14 19:56 ` Andreas K. Huettel
2015-09-14 20:19 ` hasufell
2015-09-14 20:53 ` Zac Medico
2015-09-14 20:56 ` Ulrich Mueller
2015-09-14 20:52 ` Ulrich Mueller
2015-09-14 16:38 ` Ciaran McCreesh
2015-09-14 8:18 ` Kent Fredric
2015-09-14 8:22 ` konsolebox
2015-09-14 8:28 ` Kent Fredric
2015-09-14 8:32 ` konsolebox
2015-09-14 8:41 ` konsolebox
2015-09-14 13:53 ` Manuel Rüger
2015-09-15 7:01 ` konsolebox
2015-09-14 7:58 ` [gentoo-dev] " Duncan
2015-09-14 8:16 ` konsolebox
2015-09-14 6:29 ` [gentoo-dev] " Paweł Hajdan, Jr.
2015-09-14 7:13 ` konsolebox
2015-09-14 18:07 ` Paweł Hajdan, Jr. [this message]
2015-09-14 18:54 ` Ulrich Mueller
2015-09-16 7:35 ` Kent Fredric
2015-09-15 7:21 ` konsolebox
2015-09-15 8:38 ` Ulrich Mueller
2015-09-15 8:54 ` konsolebox
2015-09-15 9:15 ` Ulrich Mueller
2015-09-15 9:31 ` Ulrich Mueller
2015-09-16 7:29 ` konsolebox
2015-09-16 7:40 ` konsolebox
2015-09-16 7:50 ` Kent Fredric
2015-09-15 12:18 ` Ciaran McCreesh
2015-09-16 7:32 ` konsolebox
2015-09-14 18:12 ` Kristian Fiskerstrand
2015-09-15 7:26 ` konsolebox
2015-09-15 7:47 ` konsolebox
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=55F70CF7.6010507@gentoo.org \
--to=phajdan.jr@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