Google Code-in

Recipes should use archives of specific commits or even better, tagged releases as SOURCE_URI instead of cloning a repository at that specific commit. Along with a CHECKSUM_SHA256 this is considered more secure.

Some more details are at http://sprunge.us/AiXb

Your job is to do just that with the listed recipes below. Do make sure the recipe still works by building it. (Tip: Leave CHECKSUM_SHA256="" and try to build and have haikuporter tell you the checksum to use.)

Fix any other style issues, like over-80char-limit, typos in the description or ordering and submit your work as pull-request. See the usual wiki page "Haikuporter recipe task".

These are the recipes to work on:

• dev-util/acr/acr-0.9.9_git.recipe
• dev-util/app2png/app2png-1.0.0.recipe
• dev-util/gyp/gyp-r1948.recipe
• games-engines/eepp/eepp-hg.recipe
• games-engines/klystron/klystron-0.0.0.recipe
• games-puzzle/dynamate/dynamate-1.0.0.recipe
• games-puzzle/numptyphysics/numptyphysics-0.2_157.recipe
• games-simulation/simutrans_pak128/simutrans_pak128-nightly.recipe
• games-simulation/simutrans_pak64/simutrans_pak64-nightly.recipe
• games-strategy/homeworld_sdl/homeworld_sdl-0.6.recipe
• gnome-base/gnome_common/gnome_common-2.28.recipe
• haiku-apps/a_book/a_book-1.1.recipe
• haiku-apps/album/album-0.9.4.recipe