Skip to content

Commit dcc1ccc

Browse files
authored
Merge pull request #323 from cerna/emcapplication-introduction
Note about old and new Debian package channels
2 parents de8ed5b + bbfe492 commit dcc1ccc

File tree

2 files changed

+56
-2
lines changed

2 files changed

+56
-2
lines changed

docs/developing/emcapplication-developing.asciidoc

+2-2
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ exit
6666

6767
At the end you will have several new **.deb** files in your folder.
6868

69-
You should replace `--gid 1000`s and `--uid 1000` with numbers which you got from `id` command in previous step.
69+
You should replace `--gid 1000` and `--uid 1000` with numbers which you got from `id` command in previous step.
7070

7171
As EMCApplication packages are pinning the version of Machinekit-HAL packages dependency to one specific version, we need to pass this version string to _debian/configure_ script as `debian/configure machinekit-hal=${VERSION}`. One can use either version available from one of accessible Debian repositories, or already installed version.
7272

@@ -162,4 +162,4 @@ Machinekit-HAL project and LinuxCNC project both have certain development vector
162162

163163
This way the _apt_ will make sure that the correct version of Machinekit-HAL is installed for the EMCApplication issue-less operation.
164164

165-
Using the _**mk-build-deps**_ script from the _devscripts_ package for creating environment capable of problem-less building of packages by invocating `dpkg-buildpackage` or compiling and linking the software during **R**un-**I**n-**P**lace build needs the `debian/control` file with correctly stated `Build-Depends: machinekit-ha (=` dependency. This is why we need to pass the _machinekit-hal_ package version early in stage when calling the `debian/configure machinekit-hal=${VERSION}` script.
165+
Using the _**mk-build-deps**_ script from the _devscripts_ package for creating environment capable of problem-less building of packages by invocating `dpkg-buildpackage` or compiling and linking the software during **R**un-**I**n-**P**lace build needs the `debian/control` file with correctly stated `Build-Depends: machinekit-hal (=` dependency. This is why we need to pass the _machinekit-hal_ package version early in stage when calling the `debian/configure machinekit-hal=${VERSION}` script.

docs/getting-started/installing-packages.asciidoc

+54
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,60 @@
33

44
:skip-front-matter:
55

6+
= OLD and NEW Debian package repositories
7+
8+
Currently, the situation in Machinekit it such that there are two channels from which one can install Machinekit binaries. The newer version is using the https://cloudsmith.io/~machinekit/repos[Cloudsmith service] with repositories https://cloudsmith.io/~machinekit/repos/machinekit/packages/[Machinekit] (with dependency packages common to all other repositories), https://cloudsmith.io/~machinekit/repos/machinekit-hal/packages/[Machinekit-HAL] (with packages from the https://github.com/machinekit/machinekit-hal[Machinekit-HAL project]) and https://cloudsmith.io/~machinekit/repos/emcapplication/packages/[EMCApplication] (with packages from the https://github.com/machinekit/emcapplication[EMCApplication project]. You will need to have usually two or all three set up on you local machine to install Machinekit-HAL or EMCApplication.
9+
10+
To set up, you should follow instruction from Cloudsmith landing page of respective repository under _**S**et-**M**e-**U**p_ icon (here for example for https://cloudsmith.io/~machinekit/repos/machinekit-hal/setup/#formats-deb[Machinekit-HAL]):
11+
12+
[source,bash]
13+
----
14+
sudo apt install curl
15+
curl -1sLf \
16+
'https://dl.cloudsmith.io/public/machinekit/machinekit-hal/cfg/setup/bash.deb.sh' \
17+
| sudo -E bash
18+
----
19+
20+
Or if the automatic script is causing problems, use manual procedure:
21+
22+
[source,bash]
23+
----
24+
sudo apt-get install -y debian-keyring
25+
sudo apt-get install -y debian-archive-keyring
26+
sudo apt-get install -y apt-transport-https
27+
curl -1sLf 'https://dl.cloudsmith.io/public/machinekit/machinekit-hal/cfg/gpg/gpg.D35981AB4276AC36.key' | sudo apt-key add -
28+
curl -1sLf 'https://dl.cloudsmith.io/public/machinekit/machinekit-hal/cfg/setup/config.deb.txt?distro=$(lsb_release -is | tr "[:upper:]" "[:lower:]")\&codename=$(lsb_release -cs) | sudo tee -a /etc/apt/sources.list.d/machinekit-machinekit-hal.list'
29+
apt-get update
30+
----
31+
32+
This setup will allow you to install the currently maintained and developed Machinekit-HAL and EMCApplication packages.
33+
34+
For EMCApplication:
35+
36+
[source,bash]
37+
----
38+
sudo apt install emcapplication
39+
----
40+
41+
For Machinekit-HAL (optionaly Machinekit-HAL-dev package):
42+
43+
[source,bash]
44+
----
45+
sudo apt install machinekit-hal
46+
sudo apt install machinekit-hal-dev
47+
----
48+
49+
For Machinekit-HAL meta-package which will install the *rt_preempt* real-time kernel:
50+
51+
[source,bash]
52+
----
53+
sudo apt install machinekit-hal-rt-preempt
54+
----
55+
56+
Everything else in pages below (_Platforms_) which uses the `deb.machinekit.io` Debian repository address is related to the **old** distribution channel. This includes mainly the now deprecated https://github.com/machinekit/machinekit[Machinekit repository] and older Machinekit-HAL and Machinekit-CNC packages. This channel **will not get any updates in the future!** However, this version is stable and tested one.
57+
58+
You can get current *Preempt_RT* patched kernel packages from official Debian repositories. (Ubuntu unfortunately at this point does not offer this service.)
59+
660
= Platforms
761

862

0 commit comments

Comments
 (0)