You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, all binary Kanto artifacts are installed to /user/local/bin. The reasoning behind that is that all the artifacts are currently distributed via a Debian package and a plain binaries archive that can be both handled manually only - not via any kind of a packages manager which acts in the general /usr/bin area.
To ensure best adoption and exploration enablement of Kanto, the first steps to make it available out-of-the-box via a public packages repo are done (i.e. the ongoing Kanto integration with Apertis). In the long run, the Debian ones are a target as well.
Furthermore, different toolings (e.g. libostree) that enable and enrich edge system and packages updates and upgrades take advantage and utilize known packaging and deployment formats and management mechanisms to provide additional capabilities on top (e.g. rollbacks, transactions, parallelism, etc.).
Thus, given the long term adoption goal and benefits, the Kanto binary artifacts installation must be adjusted accordingly - i.e. from /usr/local/bin to /usr/bin.
Currently, all binary Kanto artifacts are installed to
/user/local/bin
. The reasoning behind that is that all the artifacts are currently distributed via a Debian package and a plain binaries archive that can be both handled manually only - not via any kind of a packages manager which acts in the general/usr/bin
area.To ensure best adoption and exploration enablement of Kanto, the first steps to make it available out-of-the-box via a public packages repo are done (i.e. the ongoing Kanto integration with Apertis). In the long run, the Debian ones are a target as well.
Furthermore, different toolings (e.g. libostree) that enable and enrich edge system and packages updates and upgrades take advantage and utilize known packaging and deployment formats and management mechanisms to provide additional capabilities on top (e.g. rollbacks, transactions, parallelism, etc.).
Thus, given the long term adoption goal and benefits, the Kanto binary artifacts installation must be adjusted accordingly - i.e. from
/usr/local/bin
to/usr/bin
.Tasks:
The text was updated successfully, but these errors were encountered: