From owner-freebsd-ports  Wed Oct 16 12:47:31 1996
Return-Path: owner-ports
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id MAA00171
          for ports-outgoing; Wed, 16 Oct 1996 12:47:31 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA00162
          for <freebsd-ports@freebsd.org>; Wed, 16 Oct 1996 12:47:29 -0700 (PDT)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id MAA29524; Wed, 16 Oct 1996 12:46:51 -0700 (PDT)
To: Jake Hamby <jehamby@lightside.com>
cc: Soren Dayton <csdayton@midway.uchicago.edu>, Warner Losh <imp@village.org>,
        freebsd-ports@freebsd.org
Subject: Re: discussion of porting Ports to other things? 
In-reply-to: Your message of "Wed, 16 Oct 1996 11:41:34 PDT."
             <Pine.AUX.3.94.961016113735.2206A-100000@covina.lightside.com> 
Date: Wed, 16 Oct 1996 12:46:50 -0700
Message-ID: <29522.845495210@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> I would suggest anyone interested in a more portable ports-chain, consider
> reimplementing libftpio and fetch in C++, or maybe some sort of C wrapper
> to behave like 4.4BSD stdio.  Any suggestions? (and don't say STREAMS! :-)

Oh, ye gods, no!  Some things are worse than non-portability. :-(

					Jordan