From owner-freebsd-ports Thu Apr 13 15:11:58 2000 Delivered-To: freebsd-ports@freebsd.org Received: from shrimp.baynetworks.com (ns4.BayNetworks.COM [192.32.253.7]) by hub.freebsd.org (Postfix) with ESMTP id 702B637B596 for ; Thu, 13 Apr 2000 15:10:35 -0700 (PDT) (envelope-from bwithrow@engeast.BayNetworks.COM) Received: from mailhost.BayNetworks.COM (h8754.s84f5.BayNetworks.COM [132.245.135.84]) by shrimp.baynetworks.com (8.9.1/8.9.1) with ESMTP id SAA07514; Thu, 13 Apr 2000 18:05:09 -0400 (EDT) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id SAA13544; Thu, 13 Apr 2000 18:14:47 -0400 (EDT) Received: from tuva.engeast.baynetworks.com (tuva [192.32.150.102]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id SAA05046; Thu, 13 Apr 2000 18:10:01 -0400 for Received: from tuva.engeast.baynetworks.com (localhost [127.0.0.1]) by tuva.engeast.baynetworks.com (8.9.3/8.9.3) with ESMTP id SAA36536; Thu, 13 Apr 2000 18:09:49 -0400 (EDT) (envelope-from bwithrow@tuva.engeast.baynetworks.com) Message-Id: <200004132209.SAA36536@tuva.engeast.baynetworks.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brandon Fosdick Cc: "Withrow, Robert (W.) [BAY:BL60:430]" , ports@FreeBSD.ORG, bwithrow@engeast.BayNetworks.COM Subject: Re: Some new ports broken on 4.0REL In-Reply-To: Message from Brandon Fosdick of "Thu, 13 Apr 2000 17:54:56 EDT." <38F64230.F7F73FE4@glue.umd.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Apr 2000 18:09:49 -0400 From: Robert Withrow Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org bfoz@glue.umd.edu said: :- Did you update the /usr/ports/Mk directory as well? Is there a posted update to the /usr/ports/Mk directory at http://www.freebsd.org/ports/ ? Answer: No. That is why I said: :- Presumably there needs to be a ports update kit for 4.0? I quote: "The current ports tree officially supports only FreeBSD-current and FreeBSD-stable. Consequently, you may need to update a few files on your FreeBSD system to make use of ports developed after your version of FreeBSD was released. Please install one of the following depending on the release you are running. Also, if you are running FreeBSD-stable or FreeBSD-current that is more than a few days old, you are recommended to install an appropriate upgrade kit as well; the ports system is changing very fast at times. 2.2.1 to 2.2-stable upgrade kit For users of 2.2.1-release or 2.2-stable between 2.2.1-release and 2.2.2-release 2.2.2 to 2.2-stable upgrade kit For users of 2.2.2-release or 2.2-stable between 2.2.2-release and 2.2.5-release 2.2.5 to 2.2-stable upgrade kit For users of 2.2.5-release or 2.2-stable between 2.2.5-release and 2.2.6-release 2.2.7 to 2.2-stable upgrade kit For users of 2.2.6-release, 2.2.7-release, 2.2.8-release or 2.2-stable after 2.2.6-release 3.0 to 3-stable upgrade kit For users of 3.0-release or 3.0-stable after 3.0-release 3.1 to 3-stable upgrade kit For users of 3.1-release or 3.1-stable after 3.1-release 3.2 to 3-stable upgrade kit For users of 3.2-release or 3.2-stable after 3.2-release 3.3 or 3.4 to 3-stable upgrade kit For users of 3.3/3.4-release or 3.4-stable after 3.4-release These are FreeBSD packages; please use pkg_add to install them. That should enable you to use all the ports listed here. Note that it will only change just enough files to enable ports/packages to be used; for a full upgrade to 3-stable, please refer to the synchronizing your source tree section of the handbook. A full upgrade is recommended, especially if you are still using anything earlier than 2.2.7-release. Also, the 2.2.X line is now officially unsupported by ports-current; you are `on your own' if you wish to use the ports listed here, as opposed to the ones that were included in the release, on your 2.2.X system." -- Robert Withrow -- (+1 978 288 8256) BWithrow@BayNetworks.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message