From owner-freebsd-current@FreeBSD.ORG Tue Mar 20 10:40:36 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 199741065670 for ; Tue, 20 Mar 2012 10:40:36 +0000 (UTC) (envelope-from yerenkow@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id D1A3C8FC14 for ; Tue, 20 Mar 2012 10:40:35 +0000 (UTC) Received: by obbuo13 with SMTP id uo13so2031279obb.13 for ; Tue, 20 Mar 2012 03:40:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=2vKXqrJxSoY2LPdaBhEoOG1F+UXkVOdsBnJTMrD1Sco=; b=q1jEacZzpaUNXVxkfWfzeLsJ3QSGZl5KvX+EUqN2D3qOCy6L1EdfzkoFuYScGrRgDQ 5mqfq3ih938yzi1fOZJNEQwLbvgHBH2k5EHuXZpCqtEU/NFL/vQPMQir5wqYWvtBRIpZ O9VwJHd6W5fZtT6j5DoYwRWVubRR9dB1uPQf0LUvqsSdT6+XqfOqjsY+z+WbHdipjvxU 2or8R4sgRuj0/eI2M/CVoK5zqSTRkn/lxBDo1/q1RW3ip+rMUIX1hACER0WGPy5X7LQV uYxfjEKUdFY4Pxg+evwQZFm1ennrz14P/m2MjL67jD+1brRU4/TXaitTUTGvpe6LGoWC oNtg== MIME-Version: 1.0 Received: by 10.182.202.69 with SMTP id kg5mr17566879obc.35.1332240029508; Tue, 20 Mar 2012 03:40:29 -0700 (PDT) Received: by 10.182.97.228 with HTTP; Tue, 20 Mar 2012 03:40:29 -0700 (PDT) In-Reply-To: <20120320102008.GH2358@deviant.kiev.zoral.com.ua> References: <20120319213508.GA1692@azathoth.lan> <20120320091935.GF1692@azathoth.lan> <20120320102008.GH2358@deviant.kiev.zoral.com.ua> Date: Tue, 20 Mar 2012 12:40:29 +0200 Message-ID: From: Alexander Yerenkow To: current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: ABI/architecture identification for packages X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2012 10:40:36 -0000 IMHO, 32 / 64 = easily parsable and represent integer. i386/amd64 - wellknown names, but this info about processor bits not lies in math. My point is i386 is arch, so can be kept, while 32 is processor bit count. If you'll keep 32/64 various checks in side software will be simple (if you have 32 bit processor, then this info is bundled in "32"), while if you consider using "i386" string as storage of information about "32" bit, it not so elegant. Also, linuxes has come to i386- i586- i686- mess, and many their scripts looks overbloated when they checks if system really 32 bit. Just my point of view :)