View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005616 | GNUnet | documentation | public | 2019-02-28 11:17 | 2019-04-03 16:55 |
| Reporter | nikita | Assigned To | nikita | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Target Version | 0.11.1 | Fixed in Version | 0.11.1 | ||
| Summary | 0005616: build system integration for doc folder does not work as intended | ||||
| Description | expectation: * --disable-documentation does not build doc/handbook * --disable-documentation does install doc/man/man1 + doc/man/man5 * if --disable-documentation and --enable-texi2mdoc-generation are both true, texi2mdoc rule (inside doc/handbook and doc/tutorial) builds an output of the texi files and puts them in doc/man/man7/ reality: * --disable-documentation implies not installing doc/man/* * effects on texi2mdoc: does not build at all if --disable-documentation is passed to configure (confirmed.) this was observed doing tests with my local branch of pkgsrc-wip package for gnunet | ||||
| Tags | No tags attached. | ||||
|
|
This can be resolved by untangling the new structure in doc and the makefiles in there, as well as their include/exclude statements for conditional variables. |
|
|
* --disable-documentation implies not installing doc/man/* * effects on texi2mdoc: does not build at all if --disable-documentation is passed to configure (confirmed.) I have looked at this again. It works as intended. The problem here is that I need to be more specific. If someone does not want to build documentation, do I want this statement to mean "okay, I do not build and install any category of documentation at all" or do I want it to mean "okay, I do not build and install the texinfo kind documentation category but install the rest"? Before moving to texinfo we have (although in private) discussed the importance of documentation available offline. --enable-documentation is the default. distributors can override this. I think the best choice would be a more fine grained "--enable-man" as another option which then only gives you the manpages and optionally the generated mdoc pages. |
|
|
I'm testing my --enable-include-manpages now. |
|
|
texi2mdoc now generates output again after a long bikeshed painting session. previous commits fixed the other items of this ticket. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-02-28 11:17 | nikita | New Issue | |
| 2019-02-28 11:42 | nikita | Target Version | => 0.11.1 |
| 2019-02-28 11:47 | Christian Grothoff | Status | new => acknowledged |
| 2019-02-28 11:53 | nikita | Description Updated | |
| 2019-02-28 11:54 | nikita | Note Added: 0014101 | |
| 2019-02-28 12:02 | nikita | Description Updated | |
| 2019-02-28 12:08 | nikita | Description Updated | |
| 2019-04-01 14:18 | nikita | Assigned To | => nikita |
| 2019-04-01 14:18 | nikita | Status | acknowledged => assigned |
| 2019-04-01 14:18 | nikita | Status | assigned => acknowledged |
| 2019-04-01 14:46 | nikita | Note Added: 0014246 | |
| 2019-04-01 15:06 | nikita | Note Added: 0014247 | |
| 2019-04-01 21:57 | nikita | Status | acknowledged => resolved |
| 2019-04-01 21:57 | nikita | Resolution | open => fixed |
| 2019-04-01 21:57 | nikita | Fixed in Version | => 0.11.1 |
| 2019-04-01 21:57 | nikita | Note Added: 0014256 | |
| 2019-04-03 16:55 | Christian Grothoff | Status | resolved => closed |
