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 0C2141381F3 for ; Mon, 9 Sep 2013 15:19:18 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id ACB56E0B53; Mon, 9 Sep 2013 15:18:45 +0000 (UTC) Received: from mail-la0-f41.google.com (mail-la0-f41.google.com [209.85.215.41]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 811F5E0B4B for ; Mon, 9 Sep 2013 15:18:44 +0000 (UTC) Received: by mail-la0-f41.google.com with SMTP id ec20so5198919lab.28 for ; Mon, 09 Sep 2013 08:18:42 -0700 (PDT) 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:content-type; bh=gpKRPWvPcWdgDZ7qAQEHsNGY0B92pdJb6e1HjvjHtSs=; b=yuL3kCPFxZBf/sOaRST1UQV4jf2TplusCYMa9gDcfK0UtbvrVvLxCdJJfFWMySPGgR wsk68OZ8eId/s7rNkPUZLulbAieSzhQMtyP+NyK5oDMDk4sf2fsxdysjXAo8Q9oamTA8 IGbmLDlDYqoJtK0avg7mLfB3y7MUNojl6hj1TA7wS1BZ8bKTJY6rV9bzHlQTzuxf8mma Xx3D0MmhjcYCD4UkelPq2oyWY85cV3G3nR3/1fEnNAhylaGcgEg319g22caoZ3NQd6pD LNgxZMl1IysvQuygvxxbR45C13oiBc9UxdcjV0QNvAomtISELwtbMx5yAGpfrHl1w+Tt qlwQ== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.112.57.49 with SMTP id f17mr2925290lbq.26.1378739922769; Mon, 09 Sep 2013 08:18:42 -0700 (PDT) Sender: jdhore1@gmail.com Received: by 10.112.28.115 with HTTP; Mon, 9 Sep 2013 08:18:42 -0700 (PDT) In-Reply-To: <522DD0A1.5010207@libertytrek.org> References: <522DD0A1.5010207@libertytrek.org> Date: Mon, 9 Sep 2013 11:18:42 -0400 X-Google-Sender-Auth: D-RmUV4YL4PuZVU1XjHHotm_b3I Message-ID: Subject: Re: [gentoo-user] Portage 2.2.1 stabilized? From: Jeff Horelick To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=001a1133eaca559e4404e5f4e7f3 X-Archives-Salt: 2b1f0deb-626c-41cb-8905-702b29f1e377 X-Archives-Hash: 744659b80cfb82fbd17710920958b1a6 --001a1133eaca559e4404e5f4e7f3 Content-Type: text/plain; charset=ISO-8859-1 On 9 September 2013 09:44, Tanstaafl wrote: > Wow... just noticed an update is available which, for me, means it has > been stabilized (at least on amd64)... > > You'd think this would rate a news item and/or other major announcement, > considering how long it has taken to get here... > > Anyway, really glad to see this happen, and thanks to the devs for getting > it here! > > Now to wait a few days to see if there is any breakage to report (not > worried about it really, though, since it has actually gotten a ton of > testing over the last year or two)... > > I agree that this kind of deserves a news post just because of how momentous the occasion is, however there should not be many breakages from this as most of the features have already been in the last stable portage (such as sets and preserved-rebuild on by default). The biggest changes are probably userpriv and usersync being on by default (which is a recent change). I don't really believe that anyone will be using programmatic custom sets for a while now, which is the last feature to not be back-patched to 2.1 --001a1133eaca559e4404e5f4e7f3 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On 9 September 2013 09:44, Tanstaafl <= ;tanstaafl@l= ibertytrek.org> wrote:
Wow... just noticed an update is available w= hich, for me, means it has been stabilized (at least on amd64)...

You'd think this would rate a news item and/or other major announcement= , considering how long it has taken to get here...

Anyway, really glad to see this happen, and thanks to the devs for getting = it here!

Now to wait a few days to see if there is any breakage to report (not worri= ed about it really, though, since it has actually gotten a ton of testing o= ver the last year or two)...


I agree that this k= ind of deserves a news post just because of how momentous the occasion is, = however there should not be many breakages from this as most of the feature= s have already been in the last stable portage (such as sets and preserved-= rebuild on by default). The biggest changes are probably userpriv and users= ync being on by default (which is a recent change). I don't really beli= eve that anyone will be using programmatic custom sets for a while now, whi= ch is the last feature to not be back-patched to 2.1
--001a1133eaca559e4404e5f4e7f3--