| 1 |
Corbin Bird wrote: |
| 2 |
> On 02/02/2017 04:38 AM, Dale wrote: |
| 3 |
>> Corbin Bird wrote: |
| 4 |
>>> The package "sys-boot/grub:2" popped this warning during updates : |
| 5 |
>>> |
| 6 |
>>>> Problems with installed bash completions were found: |
| 7 |
>>>> |
| 8 |
>>>> grub: 'have' command is deprecated and must not be used. |
| 9 |
>>>> grub: incorrect name, no completions for 'grub' command defined. |
| 10 |
>>>> grub-mkconfig: missing alias (symlink) for completed command. |
| 11 |
>>>> grub-mkpasswd-pbkdf2: missing alias (symlink) for completed command. |
| 12 |
>>>> grub-mkrescue: missing alias (symlink) for completed command. |
| 13 |
>>>> grub-reboot: missing alias (symlink) for completed command. |
| 14 |
>>>> grub-editenv: missing alias (symlink) for completed command. |
| 15 |
>>>> grub-set-default: missing alias (symlink) for completed command. |
| 16 |
>>>> grub-mkimage: missing alias (symlink) for completed command. |
| 17 |
>>>> grub-sparc64-setup: missing alias (symlink) for completed command. |
| 18 |
>>>> grub-bios-setup: missing alias (symlink) for completed command. |
| 19 |
>>>> grub-script-check: missing alias (symlink) for completed command. |
| 20 |
>>>> grub-probe: missing alias (symlink) for completed command. |
| 21 |
>>>> grub-mkfont: missing alias (symlink) for completed command. |
| 22 |
>>>> grub-install: missing alias (symlink) for completed command. |
| 23 |
>>> No "grub" entries found at all in "/usr/share/bash-completions". |
| 24 |
>>> |
| 25 |
>>> Is it correct to assume any "bash-completions" are strictly personal |
| 26 |
>>> choice and NOT technically required? |
| 27 |
>>> |
| 28 |
>> I emerged grub here to see if I would get any of those messages. I |
| 29 |
>> didn't. It merged cleanly as far as I can tell. This is the version I |
| 30 |
>> have: |
| 31 |
>> |
| 32 |
>> sys-boot/grub-2.02_beta3-r1 |
| 33 |
>> |
| 34 |
>> As far as your question, the package itself should work with or without |
| 35 |
>> bash-completion. As far as I know, it only affects using tab to |
| 36 |
>> complete commands/options. |
| 37 |
>> |
| 38 |
>> Dale |
| 39 |
>> |
| 40 |
>> :-) :-) |
| 41 |
>> |
| 42 |
> |
| 43 |
> I should have mentioned the package "app-shells/bash-completion" was |
| 44 |
> installed. My mistake. |
| 45 |
> |
| 46 |
> So, I will treat "bash-completions" as optional. |
| 47 |
> |
| 48 |
> For your efforts and time, Thank You. |
| 49 |
> |
| 50 |
> |
| 51 |
|
| 52 |
I sort of figured it was. I didn't get those messages here so I suspect |
| 53 |
that something isn't normal about what you are getting. I just don't |
| 54 |
know why that is. The only mention of bash in what is installed here is |
| 55 |
this: |
| 56 |
|
| 57 |
root@fireball / # equery f grub | grep bash |
| 58 |
/usr/share/bash-completion |
| 59 |
/usr/share/bash-completion/completions |
| 60 |
/usr/share/bash-completion/completions/grub |
| 61 |
root@fireball / # |
| 62 |
|
| 63 |
I would think that should be the same here, unless we have different USE |
| 64 |
flags. There was no mention of it during the emerge process. Either |
| 65 |
way, grub should work just fine. |
| 66 |
|
| 67 |
On another note, I've noticed some bash completions not working that |
| 68 |
used to. I'm not sure what is up there. Related, don't know. |
| 69 |
|
| 70 |
You're welcome. |
| 71 |
|
| 72 |
Dale |
| 73 |
|
| 74 |
:-) :-) |
Archives