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 655401387D3 for ; Sun, 26 Oct 2014 08:56:15 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1D51BE0B93; Sun, 26 Oct 2014 08:56:09 +0000 (UTC) Received: from smarthost01c.mail.zen.net.uk (smarthost01c.mail.zen.net.uk [212.23.1.5]) by pigeon.gentoo.org (Postfix) with ESMTP id 20026E0898 for ; Sun, 26 Oct 2014 08:56:07 +0000 (UTC) Received: from [82.69.80.10] (helo=wstn.localnet) by smarthost01c.mail.zen.net.uk with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1XiJcM-00082I-Rk for gentoo-user@lists.gentoo.org; Sun, 26 Oct 2014 08:56:06 +0000 From: Peter Humphrey To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Moving the portage tree to /var Date: Sun, 26 Oct 2014 08:56:06 +0000 Message-ID: <2317632.3ZQS6Drju1@wstn> Organization: Society for Retired Gentlefolk User-Agent: KMail/4.12.5 (Linux/3.14.14-gentoo; KDE/4.12.5; x86_64; ; ) In-Reply-To: <544BD391.7070102@gentoo.org> References: <4473472.7D6UrCk1jI@wstn> <544BAC39.3050505@libertytrek.org> <544BD391.7070102@gentoo.org> 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 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Originating-smarthost01c-IP: [82.69.80.10] X-Archives-Salt: fe6de24e-5dbf-4033-87fb-184f45d8a65f X-Archives-Hash: 3d5855533500686acf8c1210b50756e0 On Saturday 25 October 2014 12:45:05 Michael Orlitzky wrote: > On 10/25/2014 09:57 AM, Tanstaafl wrote: > > On 10/7/2014 6:03 PM, Mick wrote: > >> On Tuesday 07 Oct 2014 22:56:28 Mike Gilbert wrote: > >>> Quite the opposite. Ideally, you should remove the PORTDIR setting > >>> from make.conf. repos.conf is the newer, more flexible way to > >>> configure it. > >>> > >>> Unfortunately, that will break some of the third-party portage tools > >>> which parse make.conf directly. > >> > >> ... so are we supposed to guess this, wait for a news > >> article somewhere, or will it show up in an emerge log somewhere? > > > > So... would appreciate a response from someone who knows. > > > > I really dislike making systemic changes like this without really solid > > guidance on how (and hopefully the why too)... > > I'm only guessing, but I don't think PORTDIR is going away for a while. > Eventually, portage will probably begin to warn you if you have PORTDIR > set in your make.conf, and will tell you to move your settings to > repos.conf (with a pointer to the man page or wiki). That'll stick > around for another while. Then, you'll get a news item telling you that > PORTDIR is going away in a month or so. > > Finally, your shit will stop working and that's your final warning =) > > More realistically, the portage upgrade might die or ewarn loudly if you > still have PORTDIR set. Never mind PORTDIR; it would have been considerate to give a hint that the new repos.conf directory had been introduced, and what it portended. -- Rgds Peter