This repository provides WIBU customer runtimes in linux package manager friendly manner.
The software belongs to and is developed by WIBU-SYSTEMS AG and can be downloaded on their website as well.
WIBU-SYSTEMS AG allows voraus robotik GmbH to redistribute the runtimes for you, our customers, free of charge1.
At first the maintainers publickey should be installed as trusted for apt
packages like this:
curl -s --compressed https://wibu-packages.vorausrobotik.com/ubuntu/wibu-packages-maintainers.gpg | gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/wibu-packages-maintainers.gpg > /dev/null
Afterwards this repo can be added to the apt
package sources:
echo "deb [signed-by=/etc/apt/trusted.gpg.d/wibu-packages-maintainers.gpg] https://wibu-packages.vorausrobotik.com/ubuntu/ ./" | sudo tee /etc/apt/sources.list.d/voraus-wibu.list
At this point the package manager can update its sources and be used to install e.g. codemeter-lite
.
sudo apt update
sudo apt install codemeter-lite
From this point on the package receives updates upon regular apt upgrade
calls.
Caution
While the repo itself (folder structure, CI, ...) is licensed as MIT, the packages themselves are NOT. The license conditions of WIBU-SYSTEMS AG apply to these packages.
As stated above, the packages are property of WIBU-SYSTEMS AG. We are only allowed to redistribute them. Their license is contained within the packages itself and is not affected by the MIT license of the rest of this repository.
For development purposes it might be interesting to deploy e.g. the ubuntu repo locally.
In one terminal a webserver should be launched:
cd ubuntu/
python -m http.server 8080
While in another terminal, the installation of both the public key and the sources list can take place:
curl -s --compressed http://localhost:8080/wibu-packages-maintainers.gpg | gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/wibu-packages-maintainers.gpg
echo "deb [signed-by=/etc/apt/trusted.gpg.d/wibu-packages-maintainers.gpg] http://localhost:8080 ./" | sudo tee /etc/apt/sources.list.d/localrepo.list
sudo apt-get update
After this, the repo can be used as in production. Please note that it's not a good idea to have both the production and the development repo activated at the same time.