Open thedavidmeister opened 4 years ago
@DrewMcArthur unfortunately the issue is a bit more subtle than that
the thing that consumes the scaffolding currently is a rust binary that follows the release cycle of the holochain conductor itself
tied into that repository is the HDK that also follows the same release cycle
whatever is pushed out by this scaffolding and the HDK need to line up.. but also we have a QA process where we don't put new versions of what comes from the upstream binary build process into the "love" (fully QA'd and released and ready for general consumption) branch in holonix downstream
this means that we don't have a way at the moment of making a version of hc
and the HDK separately such that we can manage the scaffolding to service both simultaneously across dependency upgrades
i think the way to resolve this is to not have HDK, hc
and holochain
all locked to the same release process and cycle, and depencency graph, so the scaffolding can track HDK depencencies without worrying about what holochain
might need
CC: @freesig @philipbeadle @zippy
hAppy tam has built a holonix scaffold.
try this out nix-shell https://github.com/holochain/holonix/archive/create-happ.tar.gz
then
hn-happ-create your-project-name
not sure if this is what the ticket is referring to, but it seems like the zome generation currently has the wrong cargo versions - i'm getting
so adding basic cargo version tests would prevent this, or let someone know they're out of date.
Anyone know where i can find the most recent version of these packages?