From owner-freebsd-stable@FreeBSD.ORG Wed Sep 3 14:05:10 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 07F3FF40 for ; Wed, 3 Sep 2014 14:05:10 +0000 (UTC) Received: from hades.sorbs.net (hades.sorbs.net [67.231.146.201]) by mx1.freebsd.org (Postfix) with ESMTP id D87131D70 for ; Wed, 3 Sep 2014 14:05:09 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from isux.com (firewall.isux.com [213.165.190.213]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0NBB0041HWMXEV00@hades.sorbs.net> for freebsd-stable@freebsd.org; Wed, 03 Sep 2014 07:08:59 -0700 (PDT) Message-id: <54072011.7030800@sorbs.net> Date: Wed, 03 Sep 2014 16:05:05 +0200 From: Michelle Sullivan User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.24) Gecko/20100301 SeaMonkey/1.1.19 To: Paul Mather Subject: Re: [HEADSUP] pkg(8) is now the only package management tool References: <20140901195520.GB77917@ivaldir.etoilebsd.net> <54050D07.4010404@sorbs.net> <540522A3.9050506@sorbs.net> <54052891.5000104@my.hennepintech.edu> <54052DFA.4030808@freebsd.org> <54053372.6020009@my.hennepintech.edu> <5405890F.8080804@freebsd.org> <20140902125256.Horde.uv31ztwymThxUZ-OYPQoBw1@webmail.df.eu> <5405AE54.60809@sorbs.net> <1D2B4A91-E76C-43A0-BE75-D926357EF1AF@gmail.com> <5405E4F5.4090902@sorbs.net> <5406BD65.705@digsys.bg> <5406ED34.7090301@sorbs.net> <5406F00C.6090504@digsys.bg> <358B9E99-5E02-47BA-9E30-045986150966@gromit.dlib.vt.edu> <540711FF.3050409@sorbs.net> <47F4AAAA-2D88-4F03-8602-880C4B129305@gromit.dlib.vt.edu> In-reply-to: <47F4AAAA-2D88-4F03-8602-880C4B129305@gromit.dlib.vt.edu> Cc: freebsd-stable , Daniel Kalchev X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-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, 03 Sep 2014 14:05:10 -0000 Paul Mather wrote: > As I pointed out, until fairly recently there was no such thing as a > "stable" release of the ports tree (it's traditionally been a rolling > release model, like -CURRENT). My question was to those who have been > using the "stable" branches: does it make managing ports updates > easier, or does it just concentrate all the problems into the > transition period between one quarterly branch to another? I've been > contemplating switching to the quarterly branches for production > machines, so would appreciate feedback. > >From what I hear getting things into the quarterly branches is neither automatic nor pain free so many don't do it. > Portsnap doesn't have any concept of tracking branches, so far as I > know. It would be nice to have that feature now that there are the > "stable" ports branches. > > I guess if you want to track "release" via portsnap the answer is not > to run portsnap. :-) > > (A "release" ports tree never changes, so why would you need portsnap > to track its changes, unless you're talking about updating ports from > one -RELEASE to another, like freebsd-update does for the rest of the > OS?) > Not quite - portsnap pulls security patches - it just doesn't upgrade... Also freebsd-update won't switch you to a 'stable' from 'release' etc... I think portsnap should provide 'stable' - tested, known working, security patched... and if you want bleeding edge use subversion, because you're likely to know (and accept) the consequences of such an action.... not to mention at that point you can rollback or if you are a new user that doesn't really know but followed some 'helpful' website/blog you can just 'rm -r /usr/ports && portsnap fetch extract' to get back to stability. > The designated tool for tracking branches is now Subversion. I believe > that's why they added svnlite in 10.x. > I don't have any 10.x machines yet (and might never have.) -- Michelle Sullivan http://www.mhix.org/