From owner-freebsd-announce Thu Mar 11 18:37:56 1999 Delivered-To: freebsd-announce@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id C935A151CF for ; Thu, 11 Mar 1999 18:37:51 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca14-33.ix.netcom.com [205.186.215.33]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id SAA28849 for ; Thu, 11 Mar 1999 18:37:18 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id SAA00516; Thu, 11 Mar 1999 18:35:53 -0800 (PST) Date: Thu, 11 Mar 1999 18:35:53 -0800 (PST) Message-Id: <199903120235.SAA00516@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: announce@freebsd.org Subject: HEADS UP: upgrade kits for ports-current From: asami@freebsd.org (Satoshi Asami) Sender: owner-freebsd-announce@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (I posted this yesterday but didn't see it show up, let me try from my freebsd.org address.) Hi, (This is not a real "heads up" for something that happened recently but about a misconception that has been plaguing us for the last few years.) If you intend to use ports-current with anything other than the latest 3.1-stable or 4.0-current, please get the appropriate "upgrade kit" from http://www.freebsd.org/ports/ before you send us a complaint saying "the new ports don't work with my 3.1R system!". It's not supposed to. :) If you installed 3.1R, or any other release, you got ports and packages with it; that's what we made to work on your system. For anything else, we can't guarantee that they will work. Ports and the source trees evolve together; just like you can't cvsup only part of the source tree and expect to be able to always build that utility, you can't cvsup part of the ports tree or even the entire ports tree and expect it to work unless the world is updated at the same time. This is just a simple fact of life around here, and has a lot to do with the available human processing power that we have and the amount of work we need to do. Unless you all want the ports tree to stop moving at all and have us release a 3.2R and 3.3R with the exact same set of ports and packages as 3.1R, we can't do it any other way. However, since there are lots of people who want to run ports-current without having to "make world" all the time, I have provided "upgrade kits" that will patch the minimal number of utilities so you can get most of them to work. Please read the above URL and follow the instructions. Thanks. :) Satoshi This is the moderated mailing list freebsd-announce. The list contains announcements of new FreeBSD capabilities, important events and project milestones. See also the FreeBSD Web pages at http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-announce" in the body of the message