From owner-svn-src-head@FreeBSD.ORG Fri May 23 16:45:28 2014 Return-Path: Delivered-To: svn-src-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A1E4B786; Fri, 23 May 2014 16:45:28 +0000 (UTC) Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9765A2FD1; Fri, 23 May 2014 16:45:27 +0000 (UTC) Received: by mail-wg0-f52.google.com with SMTP id l18so5145706wgh.35 for ; Fri, 23 May 2014 09:45:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=Z5W0eB0X3UGt0ZUnyRWPo47GZw2v0OPkUlKBpnqkY6A=; b=LNzCZN4s8DOiOrusuRKDo4vfcxolEhe0KuXOgMkAOh0Gr98YRubZooYCOh97zBWzfM QvveVi5foSQllnmYKsTcX9jsaiOP8lMNHzfAD/YOl7d8wmtJmy10RWwqMV5T5LLuM3j7 ZpXX8Y1pm7l4VhVyVW7DY0hCmn3jhqgbeu7zqAWHVYx146ZiLLdT5zAldnm8A+tktwL/ xH3M4NiWMe5cmJYSliX5WTrCwNIBavNoZ9/pzCrbGX5AszC/v0T1iK+34wmtv1Mr50w4 27kxYEQBSUyOojFjpHnmKigpEJ3jdUyVl9lPM89qupgnvvvXvwzaOEoUFAr9Hp2ysfrK iotg== X-Received: by 10.180.8.136 with SMTP id r8mr4313203wia.60.1400863524977; Fri, 23 May 2014 09:45:24 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id c2sm4523465wja.18.2014.05.23.09.45.23 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 23 May 2014 09:45:24 -0700 (PDT) Sender: Baptiste Daroussin Date: Fri, 23 May 2014 18:45:21 +0200 From: Baptiste Daroussin To: Nathan Whitehorn Subject: Re: svn commit: r266553 - head/release/scripts Message-ID: <20140523164521.GH72340@ivaldir.etoilebsd.net> References: <201405221922.s4MJM4Y9025265@svn.freebsd.org> <537F6706.6070509@freebsd.org> <20140523153619.GF72340@ivaldir.etoilebsd.net> <537F6EBC.3080008@freebsd.org> <20140523162020.GG72340@ivaldir.etoilebsd.net> <537F7976.3060705@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bygAmIonOAIqBxQB" Content-Disposition: inline In-Reply-To: <537F7976.3060705@freebsd.org> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: svn-src-head@FreeBSD.org, Glen Barber , svn-src-all@FreeBSD.org, src-committers@FreeBSD.org X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 May 2014 16:45:28 -0000 --bygAmIonOAIqBxQB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 23, 2014 at 09:38:14AM -0700, Nathan Whitehorn wrote: > On 05/23/14 09:20, Baptiste Daroussin wrote: > > On Fri, May 23, 2014 at 08:52:28AM -0700, Nathan Whitehorn wrote: > >> On 05/23/14 08:36, Baptiste Daroussin wrote: > >>> On Fri, May 23, 2014 at 08:19:34AM -0700, Nathan Whitehorn wrote: > >>>> Is there any chance of finally switching the pkg abi identifiers to = just > >>>> be uname -p? > >>>> -Nathan > >>> Keeping asking won't make it happen, I have explained a large number = of time why it > >>> happened, why it is not easy for compatibility and why uname -p is st= ill not > >>> representing the ABI we do support, and what flexibility we need that= the > >>> current string offers to us. > >>> > >>> if one is willing to do the work, please be my guess, just dig into t= he archives > >>> and join the pkg development otherwise: no it won't happen before a w= hile > >>> because we have way too much work on the todo and this item is stored= at the > >>> very end of this todo. > >>> > >>> regards, > >>> Bapt > >> I'm happy to do the work, and have volunteered now many times. If uname > >> -p does not describe the ABI fully, then uname -p needs changes on the > >> relevant platforms. Which are they? What extra flexibility does the > >> string give you if uname -p describes the ABI completely? > >> -Nathan > > just simple examples in armv6: > > - eabi vs oabi >=20 > OABI is almost entirely dead, and will be entirely dead soon. Maybe but still for now it is there and pkg has to work now >=20 > > - The different float abi (even if only one is supported for now others= are > > being worked on) >=20 > armv6 and armv6hf >=20 > > - little endian vs big endian >=20 > armv6 and armv6eb (though I think armv6eb support in general has been=20 > removed from the tree, but armeb is still there) what about combinaison? armv6 + eb + hf? >=20 > These all already exist. >=20 > > the extras flexibilit is being able to say this binary do support freeb= sd i386 > > and amd64 in one key, freebsd:9:x86:*, or or all arches freebsd:10:* > > arm was en example what about mips? >=20 > The second one already would work, wouldn't it? Just replacing x86:64=20 > with amd64 won't change anything. The first has to be outweighed by=20 > being able to reliably figure out where to fetch from without a lookup=20 > table. >=20 > We also added the kern.supported_archs sysctl last year to all branches= =20 > to enable figuring out which architectures a given running kernel=20 > supports (e.g. amd64 and i386 on most amd64 systems). This was designed= =20 > specifically to help pkg figure out what packages it can install. I know, it means that we can switch only when freebsd 8 and 9 are EOL which= means in a couple of years And it defeats cross installation (which is the reason why the ABI supporte= d is read from a binary and not from kernel) and last thing is the current build packages should just work meaning that = we would need to have a kind of mapping table --bygAmIonOAIqBxQB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iEYEARECAAYFAlN/eyEACgkQ8kTtMUmk6Ez5RQCguLMPi4avjhTXGN2uyGfdzO43 OU0AnRWITWirZWTBSWImGXlZeHu3klxi =+FLK -----END PGP SIGNATURE----- --bygAmIonOAIqBxQB--