| 1 |
Marius Mauch kirjoitti: |
| 2 |
> On Sat, 23 Jun 2007 17:11:16 +0300 |
| 3 |
> Petteri Räty <betelgeuse@g.o> wrote: |
| 4 |
> |
| 5 |
>> My opinion is to make it clear that the doc use flag always controls |
| 6 |
>> whether or not to install documentation and make it clear in the |
| 7 |
>> devmanual. For what gnome does, they can then add for example a |
| 8 |
>> gtk-doc use flag to control the building of the cross references and |
| 9 |
>> have the doc use flag control the installation of the bundled |
| 10 |
>> documentation. |
| 11 |
>> |
| 12 |
>> betelgeuse@pena ~ $ euse -i doc |
| 13 |
>> global use flags (searching: doc) |
| 14 |
>> ************************************************************ |
| 15 |
>> [- ] doc - Adds extra documentation (API, Javadoc, etc) |
| 16 |
>> |
| 17 |
>> INSTALL_MASK is of course a solution to not installing gtk-doc at all |
| 18 |
>> but it doesn't give me the ability to install it only for individual |
| 19 |
>> packages. |
| 20 |
>> |
| 21 |
>> What do others think? |
| 22 |
> |
| 23 |
> Maybe the flag needs to be renamed/split up to clarify it's meaning, |
| 24 |
> it's too generic in it's current form (many people enable it blindly and |
| 25 |
> don't really have any clue what the result is). |
| 26 |
> Like using USE=apidoc for API documentation, USE=extradoc for extra |
| 27 |
> user documentation (controlling PDF generation and stuff like that), |
| 28 |
> USE=rebuild-docs to replace pregenerated documentation with |
| 29 |
> updated/regenerated versions (like the gtk-doc issue), and so on (don't |
| 30 |
> know what other use cases there are for USE=doc currently). |
| 31 |
> |
| 32 |
> It's a large change, but USE=doc has been a significant problem for |
| 33 |
> quite a while already (circular deps anyone?) |
| 34 |
> |
| 35 |
|
| 36 |
That does sound like a good idea. |
| 37 |
|
| 38 |
Regards, |
| 39 |
Petteri |
Archives