From owner-freebsd-stable@FreeBSD.ORG Tue Jun 12 10:10:12 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C4AD01065678 for ; Tue, 12 Jun 2012 10:10:12 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 49D718FC26 for ; Tue, 12 Jun 2012 10:10:12 +0000 (UTC) Received: by bkvi18 with SMTP id i18so5399063bkv.13 for ; Tue, 12 Jun 2012 03:10:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/0i97FtuGu9kQsejErgW9gCMJKHtU+zadiDnHHkvg/c=; b=ZKIIQtLcUJVbGAhtDRNdRYq6lOVTDzl1civNlbiG2U89VH0aNtCAwsxSr0uNSvnX9y r7qaMURtOeoNrnsDH/JqA2pgozamGj0jpz6YNdu0KOjTOi0dqvlugmrrJ+A1vPD2OqQk r8JjNRzHfZwp/DQ0Gs/JXcWOnTg9EZZxzQs0hSDgiCi1ErdEQax5T0e5Wd5jJ2qkC71S LAvUjn77ChV5Xa6VloxXNnVGJtQVdGhuiwpy9B+fvdjC2zT+zG2AYk58QFBnQe4uS2ON xMxEhLN5/Va/RxHhYz908x0CtkBpMupsQ1mbRFg9bT+S0gegwNIZnDuupxhXvN/reEro 0HLg== MIME-Version: 1.0 Received: by 10.204.152.196 with SMTP id h4mr9207965bkw.131.1339495811197; Tue, 12 Jun 2012 03:10:11 -0700 (PDT) Received: by 10.204.171.138 with HTTP; Tue, 12 Jun 2012 03:10:11 -0700 (PDT) Received: by 10.204.171.138 with HTTP; Tue, 12 Jun 2012 03:10:11 -0700 (PDT) In-Reply-To: <201206120646.59491.hm@hm.net.br> References: <201206112335.q5BNZGPT029709@hugeraid.jetcafe.org> <7B6E5361-B109-498E-B22F-96A94DEC371B@mac.com> <201206120646.59491.hm@hm.net.br> Date: Tue, 12 Jun 2012 11:10:11 +0100 Message-ID: From: Chris Rees To: H Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: Why Are You NOT Using FreeBSD ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jun 2012 10:10:12 -0000 On Jun 12, 2012 10:48 AM, "H" wrote: > > On Monday 11 June 2012 20:59 Chuck Swiger wrote: > > Hi, Dave-- > > > > On Jun 11, 2012, at 4:35 PM, Dave Hayes wrote: > > [ ... ] > > > > > Do I have this wrong? Anyone see a problem with this picture? > > > What can we do to "just upgrade" in a safe fashion when we want to? > > > > Two things help tremendously: > > > > #1: Have working backups. If you run into a problem, roll back the > > system to a working state. If you cannot restore a working system > > easily, fix your backup solution until you can rollback easily. > > > > #2: Have a package-building box and test builds before installing > > new package builds to other boxes. Your downtime for upgrades > > to the rest of your boxes become minimized. > > > > Regards, > > > of course it helps ... > > but please do not forget that most people just want their desktop up to date > and have a working kde (or any other) environment > > I believe the ports tree simply must? should? be seen as it is, partially good > working, and partially a jorney to very dark places , depends on which ports > and how many you have installed > > in any case it is for somebody who knows what he does and can find his way out, > or is courageous, a "normal desktop user" probably is not able to upgrade kde4 > properly and ends up with an unusable machine > > > > On Monday 11 June 2012 20:20 Dave Hayes wrote: > > Rainer Duffner writes: > > > Sometimes, options only make sense in context of the selection of > > > options of other ports and it thus may no be easily explainable in one > > > line. > > > > I don't understand Are you saying this is a reason not to document what > > these options do? > > > both here deepen the "lead into the dark" theory > > > On Sunday 10 June 2012 14:10 O. Hartmann wrote: > > "portmaster" does even more damage. Sometimed a port reels in some newly > > updates, a port gets deleted. if on of the to be updated prerquisits > > fail, the port in question isn't there anymore. > > > this is caused of ports tree's install script maior logic failure, BTW by > portmaster AND portupgrade and it happens quite often, > > as already commented, nobody sits in front of the screen and watch the compile > process so this problems go under at first sight > > I think, correcting this, would help a lot and may solve a lot of existing > [hidden] problems. > > I see only one way, having a complete package collection for easy upgrade > > most of you do not like it, but you must look at the competitors, Fedoras > upgrade system works, user do not need the newest features and none of them > are essential for a desktop to work properly > > of course the package collection needs then something similar to portversion, > but not based on ports tree versions, in order to find available updates > > who then wants to customize or learn or who dares, can use the ports tree You have hit the nail right on the head there, and that is the intention with pkgng. Please feel free to have a go with it using the beta repos :) Chris