What is TASTE?

The best way to answer that, is to watch this presentation. You can also read how we use ASN.1 to automatically generate many software parts that are otherwise manually written (and tested!).

You can also watch these two videos, showcasing key features of how a system is designed in TASTE:

Our Wiki will then allow you to get more information about the many tools and technologies we make use of.

How can I install it?

There are a number of ways to install the TASTE toolchain, depending on your skill level and what you want to use the tools for.

TASTE VM : The easiest way by far is to download the 32-bit or 64-bit TASTE Virtual Machine image for VirtualBox. After selecting "File/Import Appliance..." you will be able to import the TASTE image in your local installation of VirtualBox, and boot it up. This Virtual Machine is based on the latest stable version of Debian Linux. After booting it up, the machine must be updated to get the latest versions of all TASTE tools - by executing cd ~/tool-src ; ./Update-TASTE.sh from any terminal emulator.

: The easiest way by far is to download the 32-bit or 64-bit TASTE Virtual Machine image for VirtualBox. After selecting "File/Import Appliance..." you will be able to import the TASTE image in your local installation of VirtualBox, and boot it up. from any terminal emulator. Docker If you have experience with Docker, you can build a complete Docker image (which is very similar to the Virtual Machine) by using this Dockerfile as follows: $ mkdir TASTE $ cd TASTE $ wget https://gitrepos.estec.esa.int/taste/taste-setup/raw/master/Dockerfile $ docker build -t taste . ...and then run a fresh TASTE container with proper X11 redirection, with... $ ./Docker-run.sh This will launch a Docker container able to run all TASTE applications, including the X11-based ones (e.g. the Ellidiss GUI). Note that your $HOME folder is mapped under /root/work inside the container - so save your work ONLY in there, because everything else will be deleted when the container dies. You can of course still commit the container and thus obtain your own custom TASTE images.

If you have experience with Docker, you can build a complete Docker image (which is very similar to the Virtual Machine) by using this Dockerfile as follows: ...and then run a fresh TASTE container with proper X11 redirection, with... This will launch a Docker container able to run all TASTE applications, including the X11-based ones (e.g. the Ellidiss GUI). Note that your folder is mapped under inside the container - so save your work ONLY in there, because everything else will be deleted when the container dies. You can of course still commit the container and thus obtain your own custom TASTE images. Natively In Debian-based distributions, you can try installing TASTE natively. Start by creating a new 'taste' user, and... $ git clone https://gitrepos.estec.esa.int/taste/taste-setup.git tool-src $ cd tool-src $ ./Update-TASTE.sh You'd then have to follow the prompts to fix whatever issues are detected in your configuration.

In Debian-based distributions, you can try installing TASTE natively. Start by creating a new 'taste' user, and... You'd then have to follow the prompts to fix whatever issues are detected in your configuration. chroot Finally, you can also install TASTE in a chroot - which allows you to have a native TASTE installation under non-Debian Linux distributions (e.g. SuSE, Fedora, etc). The process depends on the availability of the debootstrap tool in your distribution - after installing it, you will be able to... # mkdir /opt/stretch-chroot # debootstrap stretch /opt/stretch-chroot # mount -t proc none /opt/stretch-chroot/proc/ # mount -t sysfs none /opt/stretch-chroot/sys/ # mount -o bind /dev /opt/stretch-chroot/dev/ # mount -o bind /dev/pts /opt/stretch-chroot/dev/pts/ # chroot /opt/stretch-chroot ...and at this point, you can continue with the normal process described above for Debian-based distributions. For (almost) all intents and purposes, this chroot will behave just like a native Debian install; and thus allows you to have a "sandboxed" TASTE install that will not interfere with your main distribution. In fact, this is reason enough to employ this process even if you do have a Debian-based distribution; the chroot will contain all TASTE-related work, and will therefore leave your main distribution undisturbed.

Source code

Web resources

Almost all TASTE tools are developed in the open, and are available under Open-Source Licenses. The toolchain itself is maintained here , with all the tools' source code checked out under it, over Git submodules.The complete list of the relevant Git repositories can therefore be accessed through this one For additional documentation and material, please visit...

Support and community

If you want to discuss technical aspects or contact the developers, please use the following mailing-lists: