#
# klik (c) 2003-06 Simon Peter
#
# probono@myrealbox.com
#
# The klik client is published under the GPL
# Please do not set up your own klik-like servers,
# but join the klik project instead -
# please join #klik on irc.freenode.net
#
#
###########################################################################
# settings
APPNAME="Kommander"
DESCRIPTION="Visually draw Dialogs for KDE."
TESTED="KNOPPIX_V3.3-2003-11-14"
APPDIR="$HOME/$APPNAME"
APP="$APPDIR/usr/bin/kmdr-editor"
FILES="http://source.rfc822.org/pub/debian/pool/main/q/quanta/kommander_3.1.5-2_i386.deb"
MIMETYPES="text/kmdr"
ICON="$APPDIR/usr/share/icons/locolor/16x16/apps/kmdr/executor.png"
POSTINSTALL=""
###########################################################################
<\? include("recipes/generic-footer"); ?\>
# server-side include (PHP)
As you can see, this recipe is so easy because all the repeating stuff (like fetching and unpacking) is included server-wise from "recipes/generic-footer". For this app (Kommander), it would be extremely easy to create the recipe.
Please note that the descriptions for the klik store are taken from the variables inside the recipe.
Now you want to know what goes on in "recipes/generic-footer" for sure. So here it is:
# generic footer 0.1.1, do not change below (server incuded code)
# part of klik
# by probono
# be verbose
kdialog --yesno "Now downloading and installing $APPNAME to your home directory." --caption "klik" || exit 0
# create application directory
mkdir $APPDIR
cd $APPDIR
# get the file(s)
konsole --workdir $APPDIR --nomenubar --caption "klik" -e wget $FILES
# unpack
cd $APPDIR
unp *.deb -u 2> /dev/null
unp *.rpm 2> /dev/null
# clean up
rm -f *.rpm 2> /dev/null
rm -f *.deb 2> /dev/null
rm -f control.tar.gz data.tar.gz debian-binary 2> /dev/null
rm -rf control 2> /dev/null
# postinstall
echo $POSTINSTALL | sh
# create wrapper in application directory
echo "#!/bin/sh
# wrapper
# part of klik
# by probono
export LD_LIBRARY_PATH=$APPDIR/usr/lib/
export KDEDIRS=$APPDIR/usr/
export PATH=$APPDIR/sbin/:$APPDIR/bin/:$APPDIR/usr/bin/:$APPDIR/usr/sbin/:$PATH
$APP \$1" > $APPDIR/wrapper
chmod 777 $APPDIR/wrapper
# create nice folder icon
cat > $APPDIR/.directory <
[Desktop Entry]
Encoding=UTF-8
Icon=package
EOF
# create menu entry
cat > $HOME/.kde/share/applnk/klik/$APPNAME.desktop <
[Desktop Entry]
Encoding=UTF-8
Type=Application
Exec=$APPDIR/wrapper %f
Icon=$ICON
Comment=
Terminal=false
Name=$APPNAME
GenericName=
MimeType=$MIMETYPE
EOF
# start the application and be verbose
kdialog --yesno "Starting $APPDIR/wrapper in order to use $APPNAME." --caption "klik" && \
$APPDIR/wrapper
kdialog --msgbox "Remember, you can always start $APPNAME from the klik menu or by executing \n $APPDIR/wrapper" --caption "klik"
# important for klik not to give an error at the end
exit 0
Should a change in generic-footer be neccessary, it will be made once and all recipes using it will be updated immediately.
Of course, there also situations where generic-footer does not apply. For Windows apps, there is a wine-footer, for example. Flash is a good example for a recipe that doesn't use a footer at all, here the recipe is just:
#!/bin/sh
DESCRIPTION="Macromedia Flash Plugin."
TESTED="All Knoppix versions that have install_flashplugin.sh"
/usr/bin/install_flashplugin.sh
Eventually all of this runs inside a database which makes collaborative creation and editing of recipes easy and comfortable with a web interface.
Discussion board: discuss klik
There is a web interface to contribute recipes.
Because this software is in early pre-alpha stage, it is not released or licensed yet. Please contact the project team if you wish to join the project or if you want to reuse some of its code. Please do not fork klik at this moment, it will be opened for your contributions as soon as the fundamental design aspects are worked out.
klik is hosted by
klik 0.1 by probono