From owner-freebsd-questions@FreeBSD.ORG Mon Mar 26 23:55:57 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 42EB116A40A for ; Mon, 26 Mar 2007 23:55:57 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by mx1.freebsd.org (Postfix) with ESMTP id 2A04A13C46C for ; Mon, 26 Mar 2007 23:55:57 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from relay5.apple.com (a17-128-113-35.apple.com [17.128.113.35]) by mail-out4.apple.com (8.13.8/8.13.8) with ESMTP id l2QNtuke022588; Mon, 26 Mar 2007 16:55:57 -0700 (PDT) Received: from relay5.apple.com (unknown [127.0.0.1]) by relay5.apple.com (Symantec Mail Security) with ESMTP id DEE1029C006; Mon, 26 Mar 2007 16:55:56 -0700 (PDT) X-AuditID: 11807123-ad629bb000005a91-ec-46085d8c1bd5 Received: from [17.214.13.96] (cswiger1.apple.com [17.214.13.96]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by relay5.apple.com (Apple SCV relay) with ESMTP id CC34C30400B; Mon, 26 Mar 2007 16:55:56 -0700 (PDT) In-Reply-To: <20070326234039.GA69881@thought.org> References: <20070326234039.GA69881@thought.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <89425357-FE33-402A-B023-56CFBC91D386@mac.com> Content-Transfer-Encoding: 7bit From: Chuck Swiger Date: Mon, 26 Mar 2007 16:55:56 -0700 To: Gary Kline X-Mailer: Apple Mail (2.752.2) X-Brightmail-Tracker: AAAAAA== Cc: FreeBSD Mailing List Subject: Re: Upgrade suggestion 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: Mon, 26 Mar 2007 23:55:57 -0000 On Mar 26, 2007, at 4:40 PM, Gary Kline wrote: > > Hi Folks, > > Last night it struck me that one reason I constantly find new > ports to upgrade is that with ~17K ports, if you're running one > of the more common desktop managers and several popular apps, > there are going to be at least a dozen minor tweaks every day. Possibly, for a very busy program with multiple authors actively making changes. Normally, projects accumulate such changes and only release point version updates perhaps every month or so, and most have updates available much less often than that. > E.g.:going from foo-1.6.7_2 to foo-1.6.7_3. Portrevision bumps commonly happen when an underlying dependency changes; you generally don't get any changes to foo itself, unless the program version itself changes. > I used to run > port[upgrade|manager] twice/week. Was swamped; recently, > upgrading things daily. Since a lot of the wm ports take > > 24 hours to build/re-build, I'm pretty much wedged. Thus > this suggestion (for all port/package upgrade suites): > have a flag, say 'u' for "urgent" when *foo*" goes from > foo-1.6.7 to -1.6.8 or else when/if foo makes a critical > fix. There's an easier way: you can probably wait to rebuild ports until you see something listed in portaudit's output, or you know you want to update something being actively used to a specific known version that you need. > I Would've loved to have joined into the Coding ``love-in'' > this coming summer, but my shoulder said, "ARE YOU AN IDIOT!" > so not now. Besides, other tasks await. > > Flames to /dev/null,guys; rational responses see-vous-play. > > gary > > ....Still trying to learn French :-) "Donnez-moi tout mais le temps..." -- Napoleon -- -Chuck