From owner-freebsd-questions@FreeBSD.ORG Wed Mar 7 21:01:31 2012 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 05ABD106566C for ; Wed, 7 Mar 2012 21:01:31 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8C30E8FC08 for ; Wed, 7 Mar 2012 21:01:30 +0000 (UTC) Received: by werl4 with SMTP id l4so5383605wer.13 for ; Wed, 07 Mar 2012 13:01:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type:content-transfer-encoding; bh=WymqppiWattwpWzJW43RyJK718JkU43c7Vku8uRaLZc=; b=Z8d1YO+Bt48V6Hszvp/I6HA0HNlHc/Bqd2CyEKYSA0LEPK2PihXN6frkiCG1lrIMJt GunEWD3M0nSbsQ7WeTro4huQ9tZiNOOBrvtpOzQihB0UkjkahwYZJT2IUb1uAoVGGcuS 96nQZ/4C4LF2dpGSOZLHjxKYJnA+DG6Sd33wvfj3cbj82VVH88shUsKrJ8eJPziNj1OS mo8d7QryHi0UbDt1zYD31PBXnnK+BWXAzfLoWR3iAc5QMmsv5bo2aDoTY1p7RL8J145I ejOnGtdYDLyyVpn0Wa6rQ7lhlG+4P8Xi3KOqJb+rVxPOVhSXX1/a778uxdd0QPxAVwUV KHuA== Received: by 10.180.93.4 with SMTP id cq4mr6803283wib.21.1331154089721; Wed, 07 Mar 2012 13:01:29 -0800 (PST) Received: from gumby.homeunix.com (87-194-105-247.bethere.co.uk. [87.194.105.247]) by mx.google.com with ESMTPS id h19sm38516617wiw.9.2012.03.07.13.01.27 (version=SSLv3 cipher=OTHER); Wed, 07 Mar 2012 13:01:28 -0800 (PST) Date: Wed, 7 Mar 2012 21:01:26 +0000 From: RW To: freebsd-questions@freebsd.org Message-ID: <20120307210126.01a9c965@gumby.homeunix.com> In-Reply-To: References: X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.6; amd64-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Still having trouble with package upgrades 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: Wed, 07 Mar 2012 21:01:31 -0000 On Wed, 7 Mar 2012 11:28:47 -0500 David Jackson wrote: > One faulty argument I heard was that it is often not a good idea to > upgrade to new software release. This is an argument that you appear to have completely misunderstood. The point of suggesting that you use release package is that it's a workaround for your problems, and minor releases are not all that far apart. > As for compile options, the solution is simple, compile in all feature > options and the most commonly used settings into the binary packages, > for the standard i386 CPU. Surely that would be the standard amd64. > A good software philosophy is to allow software to work out of the > box with as little configuration as possible, but allow everything to > be configured by the user if they want, by shipping software with > reasonable defaults which can be overridden by the user. Make simple > things easy and complicated things doable. In GUI, by default, > complexity can be hidden from users, but if people want fine grain > control, they should be free to use advanced screens of the GUI to > get complex, fine grained control. In GUI design, more commonly used > settings can be provided more upfront while advanced features for use > by experts can be placed deeper in advanced or expert screens oft the > GUI. Everything should be able to be configured or accomplished by > both GUI and CLI and API. Are aware that FreeBSD is mostly a server OS? > doing any system wide all at once OS-release upgrades at all. There > is no reason why kernel and userland programs have to be upgraded at > the same time... The idea of waiting on a FreeBSD kernel release to > upgrade firefox is absurd, and the idea that firefox must be upgraded > during a kernel upgrade is also absurd. You don't have to do that, that's complete nonsense. > There really should be little reason for release upgrades anymore > these days, when the different parts of the system can be upgraded > independantly through a binary package management tool, including > kernel and user programs. > > When a new kernel is released, there is no reason to reinstall all of > the packages on the system at the same time. You reinstall packages because there are major library changes when you cross a major base-system release.