From owner-freebsd-questions@FreeBSD.ORG Sun Feb 11 00:27:02 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7ADF616A406 for ; Sun, 11 Feb 2007 00:27:02 +0000 (UTC) (envelope-from infofarmer@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.freebsd.org (Postfix) with ESMTP id 16F1A13C49D for ; Sun, 11 Feb 2007 00:27:01 +0000 (UTC) (envelope-from infofarmer@gmail.com) Received: by ug-out-1314.google.com with SMTP id 71so209861ugh for ; Sat, 10 Feb 2007 16:27:01 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=jZyKVbUcfwZtqayPkcRmcWDv8bnGma6maTfPQ+01rqSa5thc4rl0hffmw9Pq3zQPE0XiYeEtm4XSrKaAusil4np4X00LAvXBEbUuRrjSR78ZLjjzxALEFeQGYIg21zKTzCiAaRqjxVbGNgrj3OUoGvb6STAKCF0PUOl29lWP9nk= Received: by 10.78.200.3 with SMTP id x3mr5333615huf.1171153620783; Sat, 10 Feb 2007 16:27:00 -0800 (PST) Received: by 10.78.164.20 with HTTP; Sat, 10 Feb 2007 16:27:00 -0800 (PST) Message-ID: Date: Sun, 11 Feb 2007 03:27:00 +0300 From: "Andrew Pantyukhin" Sender: infofarmer@gmail.com To: Michael In-Reply-To: <45CE5846.80002@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45CE41ED.3050900@gmail.com> <20070210230636.GA5968@falcon.midgard.homeip.net> <45CE5846.80002@gmail.com> X-Google-Sender-Auth: 2512085023f8a753 Cc: FreeBSD - Questions Subject: Re: cvsup tag for ports X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Feb 2007 00:27:02 -0000 On 2/11/07, Michael wrote: > Erik Trulsson wrote: > > On Sat, Feb 10, 2007 at 02:06:37PM -0800, Michael wrote: > > > >> Hello everyone, > >> > >> I'm building a production server and I have what may seem to be a very > >> simple question so I hope it only requires a simple answer. > >> > >> As I've studied the FreeBSD Handbook as well as the man pages for this, > >> it's still not clear to me which tag I should use for a production server. > >> > >> For my sources I always use the security branch for the release we are > >> using so that they stay stable and also plug most of the security issues > >> as they arise and so the sources tag is always RELENG_6_2. > >> > >> For the ports, the default tag is always tag=. which I'm not sure is the > >> best thing for a production server since that's the tab for -CURRENT. > >> On one hand it makes sense to track that branch for ports because that's > >> where fixes would go for applications as they find them, but I'm not > >> convinced this is the best thing for a production server and wonder if I > >> should also use the security branch for the ports. > >> > >> My first question is, does any real security fixes go into the ports > >> when you pull from a security branch? In other words, do maintainers > >> actually submit fixes to that branch for the ports? > >> > >> I have a similiar question for the docs as well, should we be tracking > >> only the security branch when using cvsup for sources, ports and doc's? > >> > > > > Neither the ports tree nor the docs tree is branched. I.e. there is no > > security branch for ports. > > On the other hand you are not required to update installed ports/packages > > just because you update the ports tree. > > > > > > > What do you mean they aren't branched? Of course they are or they > wouldn't be in cvs and if I changed the tag, it wouldn't do anything > (they wouldn't change on running cvsup), but they do change (ports get > deleted/added/edited.), so I'm not following you here. > > Can you elaborate on what you mean? They are not branched, but just tagged. Tags may slip a bit while a release is being prepared, but after we ship it, the doc/ports tags are frozen no matter what happens in the world of 3d-party software.