x86_64 is used as a baseline: the "x86_64" entry, whatever status it has,
is transformed into "all", and then the other entries in ARCHITECTURES
either dropped or rearranged appropriately.
* now uses the short version for vendor and site paths: they are
supposed to be compatible for even version numbers. needs to rebuild
perl modules though.
* rebuild recipes depending on vendor_perl.
* beware though, haikuporter might wrongly select both perl 5.18 and
perl 5.26 in the chroot to satisfy the dependencies.
* Referring the current haiku version explicitly is not needed, since
the RequiresUpdater takes care of setting the version of Haiku used
for building a package.
* portVersionedName contains the secondary architecture,
so using it means secondary package builds fail.
example: $portVersionedName is libwow_x86-0.0.0 when
doing an x86 build on x86_gcc2
* We need to make sure the arch-specific site directory exists, as
otherwise CPAN's initialization code will believe that it can't
write to library directories and ask the user to pick a method of
circumventing this.
* perl-5.18.1 doesn't exhibit cpan-related problems seen with 5.10.1
* adjusted @INC such that perl modules installed to ~/config
(or ~/config/non-packaged) are picked up by a perl installed
into /system, too
* drop public libperl.so and link perl using an rpath instead
* no longer link every module built by ExtUtils::MakeMaker against
libperl.so, as that isn't required for Haiku at all
* adjust ExtUtils::MakeMaker to not use -rpath when linking dynamic
perl modules that require other libraries
be declared properly, now
* improve formatting of recipe files for better readability and better
compatibility with showing diffs (when moving specification lines)
* add/improve DESCRIPTION where it was just a copy of SUMMARY
* Also declare a resolvable named like the package, even if
similarly named cmd:* resolvable is declared.
* Add cmd: namespace to resolvables in [BUILD_[PRE]]REQUIRES
where appropriate. For some reason I thought that didn't
work (resulting in an error building the package), but
apparently I was mistaken.
* A few smaller fixes in [BUILD_[PRE]]REQUIRES.