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.
Removed the full-stop and repeating package name in SUMMARY.
Removed hard line breaks, broke up some very long paragraphs and
use bullet lists where possible.
All done by browsing through HaikuDepot. There may be (many) more left
in the whole haikuports repo...
Included 10 extended desriptions done by soyoye14 for GCI 2014
(https://www.google-melange.com/gci/task/view/google/gci2014/5240373098053632)
Removed/insert whitespace where it seems to be the custom in recipes.
Sometimes rearranged elements of a recipe (moving license and copyright
up, for example).
* 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
* Rename version: 2.5_121012 -> 2.5_2012_10_12.
* Don't put Jambase.html, Jamfile.html into development directory.
While correct in principle, it is not so nice to separate them from
Jam.html, which is mostly development documentation as well
(documenting the tool invocation and the Jam language).
waddlesplash