| 1 |
В Tue, 26 Aug 2014 12:51:22 +0200 |
| 2 |
Michał Górny <mgorny@g.o> пишет: |
| 3 |
|
| 4 |
> What needs to change? |
| 5 |
> --------------------- |
| 6 |
> |
| 7 |
> The major issue is how to switch the system properly -- preferably, |
| 8 |
> without forcing users to reinstall everything :). |
| 9 |
> |
| 10 |
> I think the best way forward is to: |
| 11 |
> |
| 12 |
> 1. Teach 'old' eselect-bashcomp to find files in the new $completionsdir |
| 13 |
> as well as the old location, and stabilize that soon. |
| 14 |
> |
| 15 |
> 2. Switch the eclass and ebuilds to use the new $completionsdir. While |
| 16 |
> at it, make sure that ebuilds install completion files whose names |
| 17 |
> conform to the new layout (portage QA check likely). |
| 18 |
> |
| 19 |
> 3. Do we need some specific documentation except for a regular news |
| 20 |
> item? Where? |
| 21 |
> |
| 22 |
> 4. Unmask the new bash-completion and eselect-bashcomp. Add a news item |
| 23 |
> explaining the sudden change :). |
| 24 |
> |
| 25 |
> Any comments? Doubts? Wishes? |
| 26 |
> |
| 27 |
|
| 28 |
Several packages install completions into compatdir |
| 29 |
(/etc/bash_completion.d) by default. And these completions are |
| 30 |
incompatible with autoloader, so they will not work if you simply |
| 31 |
install them into completionsdir and create necessary symlinks. One |
| 32 |
example is sys-boot/grub [1]. What do you plan to do with such packages? |
| 33 |
|
| 34 |
[1] https://bugs.gentoo.org/show_bug.cgi?id=477392 |
| 35 |
|
| 36 |
-- |
| 37 |
Alexander Tsoy |
Archives