public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Moving the portage tree to /var
Date: Mon, 27 Oct 2014 16:05:05 -0400	[thread overview]
Message-ID: <CAJ0EP41BkLyXDrVyJBHBSOt9jir3FTGUpy_dhXbu+yJLjR+d+Q@mail.gmail.com> (raw)
In-Reply-To: <544E97C2.2060008@gmail.com>

On Mon, Oct 27, 2014 at 3:06 PM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> On 27/10/2014 17:45, Tanstaafl wrote:
>> On 10/25/2014 12:45 PM, Michael Orlitzky <mjo@gentoo.org> wrote:
>>> On 10/25/2014 09:57 AM, Tanstaafl wrote:
>>>> On 10/7/2014 6:03 PM, Mick <michaelkintzios@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.
>>
>> Ok, but that doesn't answer the main question...
>>
>> Mike Gilbert - apparently a gentoo dev - said that ideally we should
>> remove the PORTDIR setting.
>>
>> This begs three questions...
>>
>> 1. Is this correct?
>>
>> 2. If so, is there a definitive guide/news item/post somewhere that
>> explains the details (how and why mainly)?
>>
>> 3. If not, why did Mike say this?
>
>
> Occam's razor:
>
> What Mike said probably translates best to something like this:
>
> Guys, I think it would be a good idea to get rid of PORTDIR now or soon
> seeing as we're close to being able to do it. What do you all think?
>
> The complete lack of any announcement or plan and that PORTDIR still
> works as always indicates this is probably what he meant by "should" -
> just a dev talking about an idea

My comment was based on an earlier version of portage, which didn't
really support PORTDIR overriding repos.conf very well.

It seems to work ok in the current release (2.2.14), so I suppose you
can use whichever method you prefer.

I'm not sure if the portage team has decided what to do long-term.


  reply	other threads:[~2014-10-27 20:05 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-07 15:09 [gentoo-user] Moving the portage tree to /var Peter Humphrey
2014-10-07 15:29 ` Bruce Schultz
2014-10-07 15:39   ` Peter Humphrey
2014-10-07 16:08     ` Neil Bothwick
2014-10-07 21:48       ` Mick
2014-10-07 21:56         ` Mike Gilbert
2014-10-07 22:03           ` Mick
2014-10-25 13:57             ` Tanstaafl
2014-10-25 16:45               ` Michael Orlitzky
2014-10-25 17:49                 ` Mick
2014-10-25 17:59                   ` Michael Orlitzky
2014-10-26 14:02                     ` [gentoo-user] " Martin Vaeth
2014-10-26 14:46                       ` Michael Orlitzky
2014-10-26  8:56                 ` [gentoo-user] " Peter Humphrey
2014-10-27 15:45                 ` Tanstaafl
2014-10-27 19:06                   ` Alan McKinnon
2014-10-27 20:05                     ` Mike Gilbert [this message]
2014-10-29 11:37                       ` [gentoo-user] " Martin Vaeth
2014-10-30 11:17                         ` [gentoo-user] Switch from PORTDIR and PORTDIR_OVERLAY to repos.conf - WAS: " Tanstaafl
2014-10-08 11:36           ` [gentoo-user] " Tanstaafl
2014-10-07 15:37 ` Neil Bothwick
2014-10-07 15:57 ` Tomas Mozes
2014-10-07 16:02   ` Tomas Mozes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJ0EP41BkLyXDrVyJBHBSOt9jir3FTGUpy_dhXbu+yJLjR+d+Q@mail.gmail.com \
    --to=floppym@gentoo.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox