From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1G8W0C-000496-11 for garchives@archives.gentoo.org; Thu, 03 Aug 2006 05:44:12 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.7/8.13.6) with SMTP id k735hLDI021569; Thu, 3 Aug 2006 05:43:21 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by robin.gentoo.org (8.13.7/8.13.6) with ESMTP id k735fUqd004301 for ; Thu, 3 Aug 2006 05:41:30 GMT Received: from gentoo.org (cp237988-a.mill1.nb.home.nl [84.29.235.69]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id E0786643C0 for ; Thu, 3 Aug 2006 05:41:29 +0000 (UTC) Date: Thu, 3 Aug 2006 07:44:20 +0200 From: Harald van =?utf-8?Q?D=C4=B3k?= To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] atom matching behavior Message-ID: <20060803054420.GA3698@gentoo.org> References: <20060803070735.61a1e3e9@sven.genone.homeip.net> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060803070735.61a1e3e9@sven.genone.homeip.net> User-Agent: Mutt/1.5.11 X-Archives-Salt: 2e8c486f-5cfe-4d6d-9cf7-c06e36c6bb67 X-Archives-Hash: e0a4e5d7bb5a34837cf92d4245d18329 On Thu, Aug 03, 2006 at 07:07:35AM +0200, Marius Mauch wrote: > Repost from gentoo-portage-dev[1]: > > Was just brought to my attention that the =* operator doesn't work as I > thought, as for example =foo-1.2* matches foo-1.20 as well as foo-1.2.3. > This wouldn't be a bug problem if it could be used as a general glob > operator like with =foo-1.2.*, Even if that would be supported, it wouldn't match foo-1.2, unless the meaning of * changes. > but it's use is strictly limited to the > above version (can only be used when a version component separator may > appear), so atm there is no facility to reliably lock an atom at a > specific version component when you have to account for multi-digit > components. > Now the question is if we want this glob-style behavior or not. From > the code comments it seems to be intentional, but I'd suspect that many > people share my original assumption and expect it to only match full > version components (as that is the much more common use case). Doesn't > help that the atom description in ebuild(5) doesn't specify the > behavior for this case either, > > "* means match any version of the package so long as the specified > base is matched" > > can be read both ways. > > Opinions? > > Marius For packages with YYYYMMDD versions, =c/p-2005* can make sense, and I have used this in the past. Please continue to allow that, and possibly provide an alternative syntax for what you currently expect =c/p-v* to do (=c/p-v.* -- if it doesn't require the . -- being a possibility). -- gentoo-dev@gentoo.org mailing list