perl installation directory difficulties

[Bolo <bolo%cs.wisc.edu@localhost>]

Running netbsd-3.1 with 2008Q4 pkgsrc is causing some difficulties
for me as to how non-pkgsrc perl software is installed.  I would like
to know how to go about fixing this problem so the perl packages will
be compatable with the existing collection.

The crux of the matter is that perl is installing things into the
wrong locations, instead of putting all the user-visible components
at the top level of a PREFIX directory, as is expected for top-level
user-visible components.   Now it is installing everything buried in
sub-directories of the PREFIX tree.

For example; hen Previously installing an arbitrary perl package ..

        perl Makefile.PL PREFIX=/usr/local/package-1.23

this would setup the perl package so install in

        /usr/local/package-1.23
                bin
                lib
                share/man
                etc

With primary executables and scripts in /usr/local/package-1.23/bin,
man pages and configuration tools in the expected places.  This is how
it works on the historical older NetBSD installations as well as other
platforms (which I don't maintain).

However, now with netbsd-3 and the pkgsrc-2008Q4 revision, the above
no longer works correctly.   Instead things are dropped into
        /usr/local/package-1.23/lib/perl5/site_perl/bin
and other places.

How do I get perl installing arbitrary packages to go back to
installing them the old way way so they are compatible with the
existing package collection?   No, creating a faked symlink bin,etc,man
of of a plethhora of perl packages to make them look like they should
is not an option.

I tried restoring the netbsd hacked files MM_Any.pm MM_Unix.pm and
MakeMaker.pm  in /usr/pkg/lib/perl to see if make-maker would start
working as it used to, but no joy.   Web searches and man pages don't
seem to indicateat all how to fix this problem, which is occuring
with a stock NetBSD and pkgsrc install.

Is there someway to get the netbsd pkgsrc perl installation back to working
how it used to, where things are installed normally as a software package,
and not in some sort of bizzare setup?

Thanks for any info, suggestions, or help.
Bolo -- Josef T. Burger.