From owner-freebsd-amd64@FreeBSD.ORG  Thu Mar 24 20:50:14 2005
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
Delivered-To: freebsd-amd64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D510F16A4CE
	for <freebsd-amd64@freebsd.org>; Thu, 24 Mar 2005 20:50:14 +0000 (GMT)
Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.193])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 71FC543D49
	for <freebsd-amd64@freebsd.org>; Thu, 24 Mar 2005 20:50:14 +0000 (GMT)
	(envelope-from astrodog@gmail.com)
Received: by wproxy.gmail.com with SMTP id 70so611834wra
        for <freebsd-amd64@freebsd.org>; Thu, 24 Mar 2005 12:50:13 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
	b=LXwoGvkvsrHg5vh6V8V2Kxxr0aZfv7Lxc0XEhiqlu+TKHzWH+tluzDKxONWQqgKqAT4SSKXyJzB8Cv6yHjVl5KR6/qv1QBZX+tx9dCXoxST1oD0RIo8ZyD8aKJxgzU5V5At2Ts2c6GdYTw+lI4CEVXAJqOtFH77v3TEMUpae+BY=
Received: by 10.54.99.6 with SMTP id w6mr500897wrb;
        Thu, 24 Mar 2005 12:50:13 -0800 (PST)
Received: by 10.54.40.69 with HTTP; Thu, 24 Mar 2005 12:50:13 -0800 (PST)
Message-ID: <2fd864e05032412501c001a5d@mail.gmail.com>
Date: Thu, 24 Mar 2005 12:50:13 -0800
From: Astrodog <astrodog@gmail.com>
To: freebsd-amd64@freebsd.org
In-Reply-To: <20050324201036.GF60666@dragon.NUXI.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
References: <2fd864e05032316492d805751@mail.gmail.com>
	 <20050324011220.GA81046@isis.sigpipe.cz>
	 <2fd864e050323182432f78eaa@mail.gmail.com>
	 <20050324201036.GF60666@dragon.NUXI.org>
Subject: Re: AMD64 Ports
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Astrodog <astrodog@gmail.com>
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Mar 2005 20:50:15 -0000

On Thu, 24 Mar 2005 12:10:36 -0800, David O'Brien <obrien@freebsd.org> wrote:
> On Wed, Mar 23, 2005 at 06:24:24PM -0800, Astrodog wrote:
> > How could we denote a linux32 dependancy?
> 
> I don't follow.  The current idea is that the linux_base port when
> installed for FreeBSD will install both 32-bit and 64-bit[*] bits.
> 
> [*] When 64-bit Linux support is later added.  We have enough polishing
> to do to just support all the things we've already got to the standards
> people expect of FreeBSD.
> --
> -- David  (obrien@FreeBSD.org)
> 

We have 2 problems, that I see. 

#1. Linux32 doesn't appear to be addressed for dependancies at all,
almost every linux-something port I've found, calls itsself i386 only,
and sometimes has minor RPM issues.

#2. With IA32 Compatibility, it should be possible to install
i386-only ports, and packages in quite a few cases, because of the
binary compatibility stuff. I'm not sure how this could be handled
either, since it would require a specific kernel option be enabled....
much like Linux32, I suppose.