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:

• haiku-apps/sanity/sanity-0.6.recipe
• haiku-apps/sawteeth/sawteeth-1.3.recipe
• haiku-apps/scrittore/scrittore-git.recipe
• haiku-apps/seeker/seeker-1.0.recipe
• haiku-apps/sequitur/sequitur-2.1.2.recipe
• haiku-apps/shredder/shredder-1.0.0.recipe
• haiku-apps/simplyvorbis/simplyvorbis-0.1.recipe
• haiku-apps/slayer/slayer-0.9.recipe
• haiku-apps/snapshot/snapshot-1.0.recipe
• haiku-apps/sum_it/sum_it-0.2beta.recipe
• haiku-apps/symetrie/symetrie-0.0.1.recipe
• haiku-apps/systeminfo/systeminfo-2.recipe
• haiku-apps/takenotes/takenotes-1.0.0.recipe