From owner-freebsd-stable@FreeBSD.ORG Wed Jul 7 20:40:26 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9BAF516A4D4 for ; Wed, 7 Jul 2004 20:40:26 +0000 (GMT) Received: from mproxy.gmail.com (mproxy.gmail.com [216.239.56.251]) by mx1.FreeBSD.org (Postfix) with SMTP id 8C33D43D5C for ; Wed, 7 Jul 2004 20:40:20 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by mproxy.gmail.com with SMTP id x43so290247cwb for ; Wed, 07 Jul 2004 13:40:17 -0700 (PDT) Received: by 10.11.122.7 with SMTP id u7mr541661cwc; Wed, 07 Jul 2004 13:40:17 -0700 (PDT) Message-ID: <790a9fff0407071340328e9579@mail.gmail.com> Date: Wed, 7 Jul 2004 15:40:17 -0500 From: Scot Hetzel To: "rbmailer-dev@yahoo.com" In-Reply-To: <20040707202920.15304.qmail@web12007.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20040707202920.15304.qmail@web12007.mail.yahoo.com> cc: freebsd-stable@freebsd.org Subject: Re: Can't cvsup ports? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jul 2004 20:40:26 -0000 On Wed, 7 Jul 2004 13:29:20 -0700 (PDT), rbmailer-dev@yahoo.com wrote: > Question on the current vs. RELEASE_4_9_x, though - I'm still on 4.9 & > don't want to upgrade to 4.10, right now. If I get current ports, won't > there (possibly) be 4.10 dependencies? Not sure I want that... > There is no dependency on the FreeBSD version in the ports collections. When a release is being made a tag (RELEASE_4_9_0, RELEASE_5_2_1, ...) is placed on the current head of the ports collection. These tags indicate which versions of the ports are included in the FreeBSD release. You can allways update your ports collection to HEAD of the cvs and they should build with your release. If anything breaks, then notify the maintainer and the ports mailing list. And if possible with a fix. Scot