tjorim
commented
5 months ago Should we not use the 23.3 tag as a base for the build instead of master? https://github.com/john30/ebusd/tree/23.3
Closed cociweb closed 5 months ago
tjorim
commented
5 months ago Should we not use the 23.3 tag as a base for the build instead of master? https://github.com/john30/ebusd/tree/23.3
cociweb
commented
5 months ago 23.3 is a little buggy. It cannot be compiled on alpine. Some additional includes are necessary for gcc13. amd64 is compiled properly above, but as of now I've stucked with the cross-compile stuff to arm/i386. And I also unsure about the possibility to pack all of them into one apk file.
tjorim
commented
5 months ago Good to know! Maybe it's better to build the package directly in the Dockerfile? That way it's open source and users can check the code instead of trusting a prebuilt package.
cociweb
commented
5 months ago Maybe (in longer term) we should consider to switch from alpine to debian base package. I know, that alpine fits perfectly to this project, but as I see ebus gets more priority/bandwidth from the maintainers on the debian platform.
PS: I will close this PR, since I won't have time in the near future (2-4 weeks) to make this temporal release workable on every arch.
A prebuilt version of the original Ebusd 23.3 based on the master branch code at 2024.01.23.
Note: It is highly recommend to revert the Dockerfile modifications and delete the temporal apk file from the ebusd/rootfs folder as soon as the 23.3-rc0 or the upcoming official version is released on the mainline!