chirpstack/chirpstack-gateway-os

splitout meta/receipe into own repo

toepi opened this issue · 2 comments

toepi commented

thanks for making this great product.

Summary

it would be nice if it possible to use your recipe in another build. so why not move all chripstack related recipes into it own repo and than use a submodule her.

What is the use-case?

build a own yocto image with ChirpStack components.

Can you implement this by yourself and make a pull request?

if this feature is wanted and the repository which should contains the recipes - for sure.

dougreese commented

I have the same situation, and ended up integrating the Chirpstack recipes using a sparse checkout submodule. Here is an example: https://github.com/dougreese/rpi-chirpstack-sparse

I am only including in my image:

  • chirpstack-gateway-bridge
  • chirpstack-concentratord

But additional recipes could be added, especially if creating a defined custom image.

However, I am currently having a problem using the Yocto 3.4 (honister) release: the recipes using Rust fail. Details are in pull request #83. The hardknott release should work.

brocaar commented

I'm closing this issue, as this is currently not planned. Splitting the ChirpStack Gateway OS up in multiple repositories does make the maintenance a bit more complex. Especially since there is a strong relation between the packages. E.g. the gateway-config recipe expects the configuration from the Concentratord and ChirpStack in a certain layout that is used by the ChirpStack Gateway OS.