-
Notifications
You must be signed in to change notification settings - Fork 6
Open
Description
This is based on a few observations:
- Updating checksums when changing the apps or the library crates that support them is tedious and feels meaningless because of course the checksums will change.
- The checksums are helpful when developing the build tools for ensuring that changes to the build tools don't inadvertently changes the built artifacts and that builds are reproducible.
- Build tools probably don't need to adhere to as strict dependency audits, especially when it comes to licenses.
- Though I think this could be fixed in the same repo. I can't remember why we don't, I think I either was too lazy to set it up or worried it would slow down CI.
- The only first party dependency that the two sides of the project share is vapix and it seems unlikely that this intersection would grow.
Downsides include:
- Updating the two sides together would be more difficult e.g. if
- building a new app requires new features from the build system
- the tools need example app(s) to test themselves
- Information fragmentation; it becomes harder to maintain a consistent documentation and moving information may involve commits in multiple repos which is tedious and makes it difficult to trace its origin.
Maybe this would be better as a discussion but discussions are disabled and I cannot enable them since I am no longer an admin.
Metadata
Metadata
Assignees
Labels
No labels