-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Q
Upgrade policy, what has been patched, ..
#8
Comments
The current update policy is "I'll merge nixos/master every once in a while or if there's a shiny new feature upstream that I want to use". It might be a good idea to automate this with Hercules CI scheduled effects. Weekly updates sounds good, I think. The original version of this project was a curated patchset (https://git.privatevoid.net/max/nix-super-archived). I switched away from that model because fixing patch conflicts after updating the upstream rev was a tedious task. Taking advantage of Git's conflict resolution capabilities makes this a nicer experience. I'd be okay with changing it back to the patchset style if you know a decent workflow for it. Having a place where all the changes in this fork are documented could be a decent solution to your problem as well. |
that makes sense, thank you for clarifying
haha, okay, I'll roll with this >3 Thank you for making this! |
|
Implement deduplication and add more test cases
Hi, I would like to ask whether this is going to be updated regularly. I'd really like to use it but I fear that this will just fall behind...
Additionally I would like to ask, whether it's possible to not have this as a fork but rather as a curated patchset so it's easier to see what is actually changed without grepping through the history.
Thanks in advance and thank you for making this.
The text was updated successfully, but these errors were encountered: