From owner-svn-src-all@FreeBSD.ORG Fri May 23 23:29:43 2014 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2978EA8D for ; Fri, 23 May 2014 23:29:43 +0000 (UTC) Received: from mail-ie0-f170.google.com (mail-ie0-f170.google.com [209.85.223.170]) (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 E4B282100 for ; Fri, 23 May 2014 23:29:42 +0000 (UTC) Received: by mail-ie0-f170.google.com with SMTP id at1so5759757iec.29 for ; Fri, 23 May 2014 16:29:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:from:content-type:mime-version:subject :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=4dGgW78ptA2LJK1h6q8G8Y6fB4CYAvtwWC6dkalQACo=; b=cctPBvaGlz8yzz7LSUf/ZK8LtKEoR0yvSjK1GCjSpN+5St66wURr1PfhZty5B2KcXW alNwNNQRX62w+dhUwRfrLshvHWX/hS/K4FVrrU64nVESUGc952rNfHG240P5v2GVECH7 Z+8BJsms7cWsaXz0h+ZrvJmM3Nnyg56G5HcosjGx4nKYf8zHmIpv/JDssUM91YLco3ox ZlgZKy+twq+UXxio2Sr/9yvrZVuajSi/f8xgTpPeJurRAz4mhNo06EBoyNBXoPqU76B+ onUw/0ZLZyGMobLp9lOKQpwc1raEHJjYkYdvGk19iYmgX4yujblMiOqiYE7maB9uJQq1 zG1A== X-Gm-Message-State: ALoCoQlnN16gBkCEp3atMBfS7f+n0NGjRvjLUTtpZOn9bStbYMF+8H0MRD0Zi1xpRNengLPKu4z/ X-Received: by 10.42.203.11 with SMTP id fg11mr7859161icb.17.1400887782008; Fri, 23 May 2014 16:29:42 -0700 (PDT) Received: from [10.0.0.119] (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id kw1sm7543877igb.4.2014.05.23.16.29.41 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 23 May 2014 16:29:41 -0700 (PDT) Sender: Warner Losh From: Warner Losh X-Google-Original-From: Warner Losh Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) Subject: Re: svn commit: r266553 - head/release/scripts In-Reply-To: <20140523162020.GG72340@ivaldir.etoilebsd.net> Date: Fri, 23 May 2014 17:29:48 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <201405221922.s4MJM4Y9025265@svn.freebsd.org> <537F6706.6070509@freebsd.org> <20140523153619.GF72340@ivaldir.etoilebsd.net> <537F6EBC.3080008@freebsd.org> <20140523162020.GG72340@ivaldir.etoilebsd.net> To: Baptiste Daroussin X-Mailer: Apple Mail (2.1878.2) Cc: svn-src-head@FreeBSD.org, Glen Barber , svn-src-all@FreeBSD.org, src-committers@FreeBSD.org, Nathan Whitehorn X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 May 2014 23:29:43 -0000 On May 23, 2014, at 10:20 AM, 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 = still not >>> representing the ABI we do support, and what flexibility we need = that the >>> current string offers to us. >>>=20 >>> if one is willing to do the work, please be my guess, just dig into = the archives >>> and join the pkg development otherwise: no it won't happen before a = while >>> because we have way too much work on the todo and this item is = stored at the >>> very end of this todo. >>>=20 >>> regards, >>> Bapt >>=20 >> I'm happy to do the work, and have volunteered now many times. If = uname=20 >> -p does not describe the ABI fully, then uname -p needs changes on = the=20 >> relevant platforms. Which are they? What extra flexibility does the=20= >> string give you if uname -p describes the ABI completely? >> -Nathan >=20 > just simple examples in armv6: > - eabi vs oabi > - The different float abi (even if only one is supported for now = others are > being worked on) > - little endian vs big endian All of those are encoded in the MACHINE_ARCH + freebsd version, no = exceptions on supported architectures that are tier 2 or higher. This seems like a = weak reason. > the extras flexibilit is being able to say this binary do support = freebsd i386 > and amd64 in one key, freebsd:9:x86:*, or or all arches freebsd:10:* Will there be a program to convert this new, special invention to the = standard that we=92ve used for the past 20 years? If you need the flexibility, = which I=92m not entirely sure I=92ve seen a good use case for. When would you have a x86 = binary package? Wouldn=92t it be either i386 or amd64? Warner