1 |
>>>>> On Thu, 13 Jun 2013, Samuli Suominen wrote: |
2 |
|
3 |
> On 13/06/13 07:58, Micha³ Górny wrote: |
4 |
>> Dnia 2013-06-13, o godz. 01:22:11 Samuli Suominen |
5 |
>> <ssuominen@g.o> napisa³(a): |
6 |
>> |
7 |
>>> what $subject says, |
8 |
>>> |
9 |
>>> "add support for pkg-config for migration to the new upstream |
10 |
>>> defined bash-completion directories (prereq for bug 472938)" |
11 |
>>> |
12 |
>>> http://bugs.gentoo.org/472938 |
13 |
>>> |
14 |
>>> ie. the pkg-config file shipped *now* in portage is a hack from me |
15 |
>>> to postpone this |
16 |
>>> |
17 |
>>> pretty tired so more eyes is cool ;) |
18 |
>> |
19 |
>> You mean http://thread.gmane.org/gmane.linux.gentoo.devel/85258 ? |
20 |
>> |
21 |
>> I think you've got to convince ulm in the first place. |
22 |
|
23 |
> His concerns was actually already covered by the first post and the |
24 |
> linked bug: |
25 |
|
26 |
> This is required for smooth migration path from old to new |
27 |
> directories. Back when the old thread happened, there was only one |
28 |
> possible value for completions dir, now there is two. And nothing |
29 |
> prevents upstream adding/changing the values in the .pc file yet |
30 |
> again for next release, this should be dynamic -- just like |
31 |
> $(get_udevdir), $(get_libdir) etc. |
32 |
|
33 |
Nothing is covered. If you change the installation dir for the |
34 |
completion modules, then eselect bashcomp won't be able to find them |
35 |
any more. So you need a transition plan. |
36 |
|
37 |
Ulrich |