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 <michaelkintz...@gmail.com> 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. > >> > >> <Scratches head> ... 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
