Timeline for How to manage common library dependencies to prevent cross-application breakage?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 24 at 13:03 | comment | added | Caleth | "impossibile to test since it depends heavily on running on real hardware" isn't true. You can still gate changes to the repo behind running tests on real hardware, it's just more inconvenient than if you didn't need real hardware. | |
| Apr 24 at 12:38 | comment | added | titanicsnake | ALL the code for ALL applications of a device reside in a single repository. Each device has a single repository. There is a lot of code that is common between those devices and that code is an exact copy in each repository. Since for a device all apps and shared code lives inside a single repo currently we have no way of "pinning" an app to a specific version of the shared code | |
| Apr 24 at 12:33 | comment | added | titanicsnake | I'm aware that tests would make changes less problematic and that's why I've written that sentence. Problem is that the current code is impossibile to test since it depends heavily on running on real hardware. Eliminating those dependencies would require a major refactor that is impossible because of the problem described in the post. | |
| Apr 16 at 9:37 | history | answered | Caleth | CC BY-SA 4.0 |