Regarding "correct perl module depencency" PRs

[Anton Berezin]

Hi,

There has been a number of PRs recently (an example would be 64377),
which in my opinion address the legitimate problem from the wrong angle.

> If we use per-5.6.x and later, this ports overwrite perl core modules.
> So, please correct to check the depencency on perl version and perl
> modules strictly.

The problem here is NOT the fact that a module is already present in the
perl distribution.  The actual problem is the fact that the module
installs itself in the "perl" area, as opposed to the "site" area, or
overwrites portions of the files belonging to the core module in some
other manner.

By solving the first problem, we essentially prevent ourselves from ever
updating to a version of a module, which is more recent than the one
contained in the perl distribution.

By solving the second problem, we get the potentially newer versions of
the core modules installed, and also prevent ourselves from putting a
mess of makefile's conditionals into all ports that depend on any "both
in the core and in the ports" module.

Now, I believe that the vast majority, if not all such modules already
have "CONFIGURE_ARGS= INSTALLDIRS=site" or equivalent in their port's
makefiles.  Those that don't are in a rather obvious need to be fixed.

The remaining problem is that we unfortunately do not have the manpage
separation between "perl" and "site" portions, so that there is indeed
a number of manpages that are overwritten.  I intend to fix that in the
upcoming 5.8.3 upgrade.  The question is, what do we do for 5.6?

Comments?  Suggestions?

Cheers,
\Anton.
-- 
Civilization is a fractal patchwork of old and new and dangerously new.
-- Vernor Vinge