|We don't bite newbies here... much|
First I want to emphasize that pod is plain old documentation, so no changes are welcome and will be systematically rejected (yours particularly and by ten orders of magnitude).
I love pod, and I will fight with all my might to keep pod the way pod is because pod is great. What you do with pod, and how you choose to manipulate pod, should never affect pod itself, as perl views it.
CVS ~ is just that, Concurrent Versions System, and perl it self shall not be CVS, nor shall it be altered to do magical dynamic pod.
As for pod maintenance, well, you will run into the same issue even if you have some magical software do programmatic changes to the pod, you still gotta write it ... basic documentation trap
perldoc may potentially only be modified to support such a wild feature only through the use of a non-standard switch, such as -magic, as to not interfere with the perldoc we've al known so far. Stability is key.
What you speak of (reusing and "dynamic" pod) can be easily accomplished. One can use Pod::Tree, and perhaps you ought to do just that, write a module that when fed a source file would do just what you want it to do, as perl shall never indulge such a wild, but interesting, idea.
If you ever decide to implement this, I would like to play with it, so please share if you do.
These have been my views on perl pod, and should be highly regarded (i'm not smiling).
Look ma', I'm on CPAN.