| 1 |
On Tue, 23 Jul 2019 13:38:28 +0200 |
| 2 |
Gerion Entrup <gerion.entrup@×××××.de> wrote: |
| 3 |
|
| 4 |
> What about a compromise?: |
| 5 |
> Deliver a (prebuild) manpage as package maintainer by default, but keep |
| 6 |
> a use flag "man-build" (or whatever) that builds the man page for everyone |
| 7 |
> (also the maintainer herself) with use of the crazy extra deps. So a user can |
| 8 |
> do (incomplete) version bumps and gets a manpage and the maintainer |
| 9 |
> gets the prebuild manpage in a defined way. |
| 10 |
|
| 11 |
You're missing the part where the maintainer is, by the policy, |
| 12 |
required to, for every bump: |
| 13 |
|
| 14 |
1. Ensure the generated documentation is extracted from the build |
| 15 |
2. Packaged into a tarball somewhere |
| 16 |
3. Uploaded to a server that can host that tarball |
| 17 |
4. Update the package to use that. |
| 18 |
|
| 19 |
Failure to do this will mean you're shipping out-dated documentation to |
| 20 |
the user. |
| 21 |
|
| 22 |
This series of back-flips is just not practical at present, and |
| 23 |
introduces more steps where mistakes can break the ebuild. |
Archives