From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9749 invoked by alias); 27 Nov 2006 15:26:00 -0000 Received: (qmail 9727 invoked by uid 48); 27 Nov 2006 15:25:51 -0000 Date: Mon, 27 Nov 2006 15:26:00 -0000 Message-ID: <20061127152551.9726.qmail@sourceware.org> From: "jakub at redhat dot com" To: glibc-bugs@sources.redhat.com In-Reply-To: <20061111170032.3506.guichaz@yahoo.fr> References: <20061111170032.3506.guichaz@yahoo.fr> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug libc/3506] strverscmp misbehaves with additional text after the version number X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2006-11/txt/msg00086.txt.bz2 ------- Additional Comments From jakub at redhat dot com 2006-11-27 15:25 ------- The strverscmp function really can't change at this point, it is well documented how it behaves and programs rely on its behavior. strverscmp only cares about the longest substring containing consecutive digits around the first differing byte, so not even dots mean anything to it. You are looking for a function like rpmvercmp in which provides segmented comparison. But why should that be in libc? -- What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |WAITING http://sourceware.org/bugzilla/show_bug.cgi?id=3506 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.