Currently, we are only shipping source releases. For better reach, we should provide package releases for debian/ubuntu, arch, (possibly) alpine, homebrew, and whatever windows uses. The package is technically available through CPM, but that is only relevant for other C++ developers and not for people who just want to use the tool suite.
This would preferably be done through a (series of) CI pipelines, with maybe a manual package-push step?
As an MVP implementation, we should just target one of the proposed distributions as a proof of concept and then introduce more and more distributions one by one.
sillydan1
commented
3 days ago
Currently, we are only shipping source releases. For better reach, we should provide package releases for debian/ubuntu, arch, (possibly) alpine, homebrew, and whatever windows uses. The package is technically available through CPM, but that is only relevant for other C++ developers and not for people who just want to use the tool suite.
This would preferably be done through a (series of) CI pipelines, with maybe a manual package-push step?
As an MVP implementation, we should just target one of the proposed distributions as a proof of concept and then introduce more and more distributions one by one.