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-cpp/hugen/hugen-1.recipe
• dev-embedded/arduino/arduino-1.7.7.recipe
• dev-embedded/cpcsdk/cpctools-0.3.0.recipe
• dev-embedded/lm4tools/lm4tools-0.1.3.recipe
• dev-java/rxtx/rxtx-2.2_pre2.recipe
• dev-lang/openjdk/openjdk-1.8.u40_b27.recipe
• dev-lang/v8/v8-3.16.1.recipe
• dev-libs/gnulib/gnulib-2013_12_17.recipe
• dev-libs/libsolv/libsolv-0.3.0_haiku_2013_06_16.recipe
• dev-lua/luafilesystem/luafilesystem-1.6.2_git.recipe
• dev-qt/automoc/automoc-0.9.88.recipe
• dev-qt/qsystray/qsystray-0.1.recipe
• dev-qt/qt5/qt5base-5.5.0.recipe