1 |
I emerged emacs last night, and I noticed the following: |
2 |
|
3 |
* Regenerating GNU info directory index... |
4 |
('cl', None, None, '.gz') |
5 |
('emacs', None, None, '.gz') |
6 |
('eshell', None, None, '.gz') |
7 |
('forms', None, None, '.gz') |
8 |
('ediff', None, None, '.gz') |
9 |
('ebrowse', None, None, '.gz') |
10 |
('gnus', None, None, '.gz') |
11 |
('idlwave', None, None, '.gz') |
12 |
* Processed 84 info files: 8 errors; type emerge --verbose to view |
13 |
errors. |
14 |
|
15 |
I think this happens because there is no DIR entry in those specific |
16 |
info files. Is anyone else experiencing this issue? I'm not sure if my |
17 |
system is out-of-wack, or it's an issue with such packages. The annoying |
18 |
part is that these same "errors" will show up in the output of any |
19 |
subsequent packages emerged. |
20 |
|
21 |
I'd also like to know what to do with such errors for .ebuilds i create. |
22 |
I am thinking I will patch each offending info file to include the DIR |
23 |
entry. Sound good? |
24 |
|
25 |
Thanks |
26 |
Matthew |