From owner-freebsd-questions@FreeBSD.ORG Tue Sep 4 03:15:18 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 839F116A419 for ; Tue, 4 Sep 2007 03:15:18 +0000 (UTC) (envelope-from glists@greywether.com) Received: from phaea.greywether.com (www.looseleafwomentea.com [216.182.86.132]) by mx1.freebsd.org (Postfix) with ESMTP id 69FCA13C47E for ; Tue, 4 Sep 2007 03:15:18 +0000 (UTC) (envelope-from glists@greywether.com) Received: (qmail 1007 invoked from network); 4 Sep 2007 02:45:15 -0000 Received: from unknown (HELO Feather.local) (gweb@greywether.com@70.89.113.254) by phaea.greywether.com with ESMTPA; 4 Sep 2007 02:45:15 -0000 Message-ID: <46DCCC2C.7030402@greywether.com> Date: Mon, 03 Sep 2007 20:08:28 -0700 From: Gary Affonso User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Philosophy of default "pkg_add -r" PACKAGESITE? 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: Tue, 04 Sep 2007 03:15:18 -0000 Here's one thing I've never quite understood about FreeBSD and I was hoping somebody could provide some enlightenment... I've got 6.2-release installed. By default (as you all probably know) "pkg_add -r" fetches packages from the "release" directory: ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.2-release Now here's where it gets weird for me. If I understand the FreeBSD release methodology , that "release" is a frozen-in-time snapshot of a particular release (6.2 in my case) that gets no future updates. As we move farther and farther beyond a particular releases debut-date, that snapshot (and the packages it contains) gets increasingly stale. Do I have that right? If I do, it seems to me that the absolute first thing I should do after installing a release version would be to change where "pkg_add -r" is sourcing packages from. Either to "current" if I like to live on the edge or "stable" if I want to be a more conservative. I'm curious, why does "pkg_add -r" point to the "release" snapshot of ports by default? Is the idea that a "release" is well-tested and that any deviation from that (even security or bug-fix changes) is an unknown that new users need to be shielded against when grabbing packages with "pkg_add -r"? Seems to me it would be better to have "pkg_add -r" point to stable (which, if I understand things correctly, does get updated packages). And how does one go about *permanently* changing the "pkg_add -r" target. You can set the PACKAGESITE variable in the shell which will work on a user-by-user basis but isn't there a way to centrally change PACKAGESITE without relying on each user to have properly config'd their individual shells? I know a lot of thought has gone into the current system so I'm thinking that these questions are due to the fact that I'm just not grok'ing something important about the philosophy behind all this. Any help would be greatly appreciated. - Gary