1 |
On Mon, Oct 27, 2014 at 3:06 PM, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
2 |
> On 27/10/2014 17:45, Tanstaafl wrote: |
3 |
>> On 10/25/2014 12:45 PM, Michael Orlitzky <mjo@g.o> wrote: |
4 |
>>> On 10/25/2014 09:57 AM, Tanstaafl wrote: |
5 |
>>>> On 10/7/2014 6:03 PM, Mick <michaelkintzios@×××××.com> wrote: |
6 |
>>>>> On Tuesday 07 Oct 2014 22:56:28 Mike Gilbert wrote: |
7 |
>>>>>> Quite the opposite. Ideally, you should remove the PORTDIR setting |
8 |
>>>>>> from make.conf. repos.conf is the newer, more flexible way to |
9 |
>>>>>> configure it. |
10 |
>>>>>> |
11 |
>>>>>> Unfortunately, that will break some of the third-party portage tools |
12 |
>>>>>> which parse make.conf directly. |
13 |
>>>> |
14 |
>>>>> <Scratches head> ... so are we supposed to guess this, wait for a news article |
15 |
>>>>> somewhere, or will it show up in an emerge log somewhere? |
16 |
>>>> |
17 |
>>>> So... would appreciate a response from someone who knows. |
18 |
>>>> |
19 |
>>>> I really dislike making systemic changes like this without really solid |
20 |
>>>> guidance on how (and hopefully the why too)... |
21 |
>> |
22 |
>>> I'm only guessing, but I don't think PORTDIR is going away for a while. |
23 |
>> |
24 |
>> Ok, but that doesn't answer the main question... |
25 |
>> |
26 |
>> Mike Gilbert - apparently a gentoo dev - said that ideally we should |
27 |
>> remove the PORTDIR setting. |
28 |
>> |
29 |
>> This begs three questions... |
30 |
>> |
31 |
>> 1. Is this correct? |
32 |
>> |
33 |
>> 2. If so, is there a definitive guide/news item/post somewhere that |
34 |
>> explains the details (how and why mainly)? |
35 |
>> |
36 |
>> 3. If not, why did Mike say this? |
37 |
> |
38 |
> |
39 |
> Occam's razor: |
40 |
> |
41 |
> What Mike said probably translates best to something like this: |
42 |
> |
43 |
> Guys, I think it would be a good idea to get rid of PORTDIR now or soon |
44 |
> seeing as we're close to being able to do it. What do you all think? |
45 |
> |
46 |
> The complete lack of any announcement or plan and that PORTDIR still |
47 |
> works as always indicates this is probably what he meant by "should" - |
48 |
> just a dev talking about an idea |
49 |
|
50 |
My comment was based on an earlier version of portage, which didn't |
51 |
really support PORTDIR overriding repos.conf very well. |
52 |
|
53 |
It seems to work ok in the current release (2.2.14), so I suppose you |
54 |
can use whichever method you prefer. |
55 |
|
56 |
I'm not sure if the portage team has decided what to do long-term. |