From owner-freebsd-ports Thu Oct 24 00:12:04 1996 Return-Path: owner-ports Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA21395 for ports-outgoing; Thu, 24 Oct 1996 00:12:04 -0700 (PDT) Received: from nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA21365 for ; Thu, 24 Oct 1996 00:12:00 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by nike.efn.org (8.7.5/8.7.3) with SMTP id AAA00723; Thu, 24 Oct 1996 00:11:14 -0700 (PDT) Date: Thu, 24 Oct 1996 00:11:14 -0700 (PDT) From: John-Mark Gurney X-Sender: jmg@nike Reply-To: John-Mark Gurney To: Michael Smith cc: "Eric L. Hernes" , ports@freebsd.org Subject: Re: linux_devel port-thing In-Reply-To: <199610240252.MAA04543@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 24 Oct 1996, Michael Smith wrote: > I don't think that staging it would be a good idea. What I want is > basically "fetch this monster tarball" and "extract this monster into > /compat/linux". What I'm not so sure about is which parts of the port > process it should attach to. I'm not that familiar with the ports system... but can't you over ride targets like extract, build, and clean?? just a thought... ttyl.. John-Mark gurney_j@efn.org http://resnet.uoregon.edu/~gurney_j/ Modem/FAX: (541) 683-6954 (FreeBSD Box) Live in Peace, destroy Micro$oft, support free software, run FreeBSD (unix)