From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id D0F29138247 for ; Mon, 4 Nov 2013 15:51:03 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 14769E0B2D; Mon, 4 Nov 2013 15:50:57 +0000 (UTC) Received: from mail-vb0-f45.google.com (mail-vb0-f45.google.com [209.85.212.45]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 2D227E0B28 for ; Mon, 4 Nov 2013 15:50:55 +0000 (UTC) Received: by mail-vb0-f45.google.com with SMTP id p6so1489410vbe.18 for ; Mon, 04 Nov 2013 07:50:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=fPd0UlaaC3t1mQ26A7GOy9rggFge2wLZixYCs/7sWcE=; b=jg22AH0U8eayj7lGF+KJdtJK6XoySUzNX5puKJULQkxG+//GV5YgggcqJI9gZF8SNG m9Kc5sd8kD4KZkLKHezIb266pVRexp37L/QGuoJFPVaeOT471wJ3XCZdzFOW8We8r0q8 KLJoKTQS2FzW+X05jBRcBva2FF7cwBPUAqzJq6Bg720n844fDXajGRaL5T281m1VpRfq MjegDmF5aKVBgVUV83DbShzRIJMZq9zoOtn6tIoOu/mVj3Q3N5ZLUbfVQ0hhqzfyEwu/ NoHmDJIG8NGkfgHHAYO1onkrq2Vdn0wNSn4D11RYOWJwgKGrXsxBNN1iDcf2hA5g7Ip/ oVng== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.52.230.202 with SMTP id ta10mr251702vdc.41.1383580255366; Mon, 04 Nov 2013 07:50:55 -0800 (PST) Sender: freemanrich@gmail.com Received: by 10.52.108.199 with HTTP; Mon, 4 Nov 2013 07:50:55 -0800 (PST) In-Reply-To: <20131104132834.27fe7dfb@TOMWIJ-GENTOO> References: <20131104051518.51efd36c@gentoo.org> <52775FD3.7000102@sporkbox.us> <20131104112632.0c7ff3de@gentoo.org> <52778DDC.7080407@gmail.com> <20131104132834.27fe7dfb@TOMWIJ-GENTOO> Date: Mon, 4 Nov 2013 10:50:55 -0500 X-Google-Sender-Auth: M-knmJ5olq-KC8WNtHfT1yywupU Message-ID: Subject: Re: [gentoo-dev] Re: Official way to do rolling update (Was: Re: Releng breakage with respect to move from dev-python/python-exec to dev-lang/python-exec) From: Rich Freeman To: gentoo-dev Cc: Dale K Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: bf5eafcb-4d28-4558-be7e-ebeb7708fe00 X-Archives-Hash: 7f7942f26870d910e9245f7a2320a6b7 On Mon, Nov 4, 2013 at 7:28 AM, Tom Wijsman wrote: > On Mon, 04 Nov 2013 06:06:52 -0600 > Dale wrote: > >> But after a person has used Gentoo a while, they figure out what >> process leads to the most stable update process. > > Do they? What do you consider a stable update process? > > I come across users on a daily basis which... I would love to see a simple way to invoke emerge such that it just "does the right thing" in updating the system. Its behavior would always be considered subject to change (scripts should use the long options if they don't just want the latest automagic behavior). I see this as having several benefits: 1. It is newbie friendly. Anybody can understand apt-get update, apt-get upgrade. If I told you what I invoked to do my daily updates on Gentoo it would start a religious war on whether I'm doing it right. 2. It is supportable. If a developer pushes out a commit without a news item such that a stable user runs the standard update command before the commit and after it and the second update fails, then that is a valid bug. I'm not suggesting that all such bugs are preventable/etc, but it does help get rid of the whole "you're holding it wrong" debate. 3. It is maintainable. When new portage features arise they can be added to the default behavior when appropriate, without the need to get everybody to change their command lines. 4. It is a standard. Gentoo is all about being able to deviate from the standards. However, there is still value in suggesting a best practice. Rich