Comment by JackSlateur
Comment by JackSlateur 2 hours ago
tldr: create a fork, fix the fork, use the fork. When upstream is fixed, remove your fork.
It thought that this was option #2 but apparently no
Comment by JackSlateur 2 hours ago
tldr: create a fork, fix the fork, use the fork. When upstream is fixed, remove your fork.
It thought that this was option #2 but apparently no
I guess it's a technicality because the original option #2 is permanent, while the proposed solution is theoretically temporary (IME this approach will end up being permanent too based on how many companies operate). I actually think more companies should do this pre-emptively; it's very little extra work on the happy path (i.e. 1:1 with upstream) and you're ready to go when you need to deviate or fix and gives you better isolated supply management for your dependencies.