| 1 |
> On 15 Jul 2022, at 11:17, Hans de Graaff <graaff@g.o> wrote: |
| 2 |
> |
| 3 |
> Skip building documentation rather than generating an error when rdoc is |
| 4 |
> missing but documentation is requested. rdoc should not be missing |
| 5 |
> normally, but this is a common problem when updating from one ruby |
| 6 |
> target straight to another one. There can be a gap when eselect has not |
| 7 |
> been triggered again yet for rdoc and another core ruby package may |
| 8 |
> require rdoc. This is commonly bundler since it has a +doc USE flag. |
| 9 |
> |
| 10 |
|
| 11 |
I worry a bit about silently skipping given it can go further |
| 12 |
and lead to e.g. unpredictably broken binpkgs. |
| 13 |
|
| 14 |
I'd probably prefer not doing +doc but I assume it's there |
| 15 |
for a reason. |
| 16 |
|
| 17 |
Anyway, the situation is what it is until we get a ruby-exec |
| 18 |
or similar, so go for it. Thanks for figuring out a workaround, |
| 19 |
as this one is often a bit painful. |
| 20 |
|
| 21 |
> Signed-off-by: Hans de Graaff <graaff@g.o> |
| 22 |
> --- |
| 23 |
|
| 24 |
Best,, |
| 25 |
sam |
Archives