| 1 |
Michael Cummings wrote: |
| 2 |
|
| 3 |
> OK, no secret that wheels have been turning on how to handle this. |
| 4 |
> Ultimately, the collision protect madness (if your not familiar with |
| 5 |
> it, check bug 71659 should whet your appetite) stems from man page |
| 6 |
> conflicts. I've gone through every package on my boxes, and the funny |
| 7 |
> thing is, the only thing (no matter what actually uses the perl-module |
| 8 |
> eclass) that installs anything in man3 are perl module pods being |
| 9 |
> converted. Any apps we have that happen to use the eclass also simply |
| 10 |
> don't generate man3 pages (or, if they do, it's in addition to any |
| 11 |
> inline pods, not in place of). Below patch is to disable the pod2man |
| 12 |
> generation and should have the quick, efficient effect of stopping 98% |
| 13 |
> of our collision protects in perl. Let me know if you have any |
| 14 |
> thoughts, probably will commit this tomorrow if I don't hear anything. |
| 15 |
> |
| 16 |
> ~mike |
| 17 |
|
| 18 |
|
| 19 |
Isn't there a more elegant way than preventing pod being converted to |
| 20 |
man pages? |
| 21 |
I personally don't `man` my modules, so I won't suffer from it, but |
| 22 |
maybe someone out there does? (otherwise, why is pod2man even being |
| 23 |
invoked?). |
| 24 |
|
| 25 |
Just my $.02... |
| 26 |
|
| 27 |
--Yuval |
| 28 |
-- |
| 29 |
gentoo-perl@g.o mailing list |
Archives