1 |
On 2021-07-20, John Covici wrote: |
2 |
|
3 |
> On Tue, 20 Jul 2021 02:53:30 -0400, |
4 |
> Neil Bothwick wrote: |
5 |
>> |
6 |
>> [1 <text/plain; US-ASCII (quoted-printable)>] |
7 |
>> On Tue, 20 Jul 2021 07:36:27 +0100, (Nuno Silva) wrote: |
8 |
>> |
9 |
>> > As this is a problem with generating documentation, have you tried the |
10 |
>> > following as a workaround?: |
11 |
>> > |
12 |
>> > USE=-doc emerge -1a media-libs/harfbuzz |
13 |
>> |
14 |
>> It is recommended that you do not enable the doc USE flag globally, but |
15 |
>> only for those packages where you need the extra documentation. |
16 |
>> |
17 |
>> % grep \^doc /var/portage/profiles/use.desc |
18 |
>> doc - Add extra documentation (API, Javadoc, etc). It is recommended |
19 |
>> to enable per package instead of globally |
20 |
> Well, I finally did manage to get harfbuzz installed which brings up |
21 |
> another question. First, I tried to find the package for the |
22 |
> /usr/bin/gtkdoc packages and found none. So, on a hunch, I emerged |
23 |
> dev-utils/gtk-doc and discovered I did not have the package in my |
24 |
> install. So, I did it anyway and after that harfbuzz installed. So, |
25 |
> the question is, should I put that in my world file -- which seems |
26 |
> wrong to me, or is there a missing dependency somewhere or what? |
27 |
|
28 |
If I'm reading the ebuild correctly, currently having USE=-doc does not |
29 |
disable building the documentation. Setting USE=doc would probably have |
30 |
worked as a workaround, because then emerge would pull gtk-doc as a |
31 |
dependency. |
32 |
|
33 |
I've mentioned this problem on IRC, but I haven't filled anything at |
34 |
bugzilla. |
35 |
|
36 |
|
37 |
I wonder if replacing |
38 |
|
39 |
$(meson_native_use_feature doc) |
40 |
|
41 |
with |
42 |
|
43 |
$(meson_native_use_feature doc docs) |
44 |
|
45 |
is enough? (I haven't tested it, though) |
46 |
|
47 |
-- |
48 |
Nuno Silva |