Skip to content

crashplan: refactor allowing local version bumping with overrideAttrs #26666

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

Conversation

forficate
Copy link
Contributor

@forficate forficate commented Jun 17, 2017

Motivation for this change

It was not possible to increment the version of crashplan locally using overrideAttrs due to the hardcoded version in the installPhase.

Now a user can modify the src and name values to increment the version manually in their configuration using overrideAttrs.

Things done
  • Tested using sandboxing
    (nix.useSandbox on NixOS,
    or option build-use-sandbox in nix.conf
    on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • Linux
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

cc @sztupi @domenkozar @jerith666

Sorry, something went wrong.

It was not possible to increment the version of crashplan locally using overrideAttrs due to the hardcoded version in the installPhase.

Now a user can modify the `src` and `name` values to increment the version manually in there configuration using overrideAttrs.
@mention-bot
Copy link

@ajevans85, thanks for your PR! By analyzing the history of the files in this pull request, we identified @jerith666, @sztupi and @domenkozar to be potential reviewers.

@jerith666
Copy link
Contributor

jerith666 commented Jun 17, 2017

Seems simpler to do this by abandoning the let ... in and just moving the version and rev properties into the mkDerviation rec, as in my 2cb4b8f. Does that allow the same sort of local overriding you're aiming for?

@forficate
Copy link
Contributor Author

Yes that works. A user can override the version and src attributes to bump the version manually if needed, ie to 4.8.3.

@jerith666
Copy link
Contributor

Okay, I opened #26705 for my change then.

@ajevans85, are you planning to open a PR for the 4.8.2 -> 4.8.3 update, or shall I?

@forficate
Copy link
Contributor Author

I was planning to do that after this PR had been merged to prevent merge conflicts.

I'll close this now you have opened #26705 and can raise a pr 4.82 -> 4.8.3 once #26705 is merged.

@forficate forficate closed this Jun 19, 2017
@forficate forficate mentioned this pull request Jun 24, 2017
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants