Changes

* ''push'', rsync dist/ to the server

* ''push'', rsync dist/ to the server

* ''lint'', check feed file on the server<br>will run [http://0install.net/feedlint.html FeedLint] application for http://download.sugarlabs.org/services/ feed

* ''lint'', check feed file on the server<br>will run [http://0install.net/feedlint.html FeedLint] application for http://download.sugarlabs.org/services/ feed

* ''build-command'', for services that have compilation stage, command how to build binaries<br>Its value is a shell command, executed inside the build directory $BUILDDIR. It must compile the source in $SRCDIR, putting the final result (ready for distribution) in $DISTDIR. If this command starts to get complicated, you should move it to a script (either inside the main source archive or in a separate dependency) and just set this attribute to the command to run the script.<br>For example, followed command builds regular autotools based project

* ''build-command'', for services that have compilation stage, command how to build binaries<br>Its value is a shell command, executed inside the build directory $BUILDDIR. It must compile the source in $SRCDIR, putting the final result (ready for distribution) in $DISTDIR. If this command starts to get complicated, you should move it to a script (either inside the main source archive or in a separate dependency) and just set this attribute to the command to run the script.<br>'''NOTE''' This command will be executed not only in service developer environment but also on user side if there proper binaries wasn't found, so do not use here any development related dependencies like ''autogen.sh''<br>For example, followed command builds regular autotools based project

  "$SRCDIR"/configure --prefix="$DISTDIR" && make install

  "$SRCDIR"/configure --prefix="$DISTDIR" && make install