Skip to content
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

vimPlugins.defx-nvim: init at 2019-08-19 #67160

Merged
merged 1 commit into from Sep 22, 2019

Conversation

@ldelelis
Copy link
Contributor

commented Aug 21, 2019

Motivation for this change
Things done

Comparing my changes to similar plugin init PRs, I see I somehow got a lot more automatic changes applied to generated.nix. I prepared this following the steps outlined in here. Is this correct?

  • [ x ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • [ x ] NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.
Notify maintainers

cc @

@timokau

This comment has been minimized.

Copy link
Member

commented Aug 25, 2019

Why is the commit message saying init at 1.0? Is there an actual 1.0 release? Otherwise it should just be init at 2019-08-19.

Comparing my changes to similar plugin init PRs, I see I somehow got a lot more automatic changes applied to generated.nix
It looks like this just happened to be an unusually active week for vim plugin maintainers. Also for some reason readline-vim got reordered in generated.nix, not sure what's up with that. But it seems harmless.

@ldelelis

This comment has been minimized.

Copy link
Contributor Author

commented Aug 26, 2019

@timokau

The github repo for Defx shows a 1.0 tagged release. However I'm not sure if that's what nixpkgs looks for when building derivations for vim plugins.

@timokau

This comment has been minimized.

Copy link
Member

commented Aug 26, 2019

Since vim plugins usually don't have releases and are intended to be shipped straight from master, the nixpkgs vim infrastructure doesn't look from releases but instead takes the latest master commit. If you want to use versions instead, you have to side-step the automated infrastructure. Please try to find out (or ask) if this plugin is intended to be used from master or from the tagged version.

@ldelelis

This comment has been minimized.

Copy link
Contributor Author

commented Sep 8, 2019

@timokau

I've tried getting in contact with Shougo multiple times through email now, but I can't get ahold of them. However, after confirming in a different distro how plugin managers handle it, they all pull from master, rather than one of the releases. What should I do here regarding the commit message?

@timokau

This comment has been minimized.

Copy link
Member

commented Sep 20, 2019

When we track master instead of releases, we usually use the date of the latest commit as the version. So you need to find out when the latest commit on master was made and then amend the commit to init at 2019-xx-xx.

@ldelelis ldelelis force-pushed the ldelelis:vim-plugins-shougo-defx branch from 237d3f0 to fd90f36 Sep 22, 2019
@ldelelis ldelelis changed the title vimPlugins.defx-nvim: init at 1.0 vimPlugins.defx-nvim: init at 2019-08-19 Sep 22, 2019
@ldelelis

This comment has been minimized.

Copy link
Contributor Author

commented Sep 22, 2019

Is this ok now? I've rebased to an updated master, amended my last commit to fix the init message, and force-pushed the result to my current branch

Copy link
Member

left a comment

Yes, looks good now. Thank you!

@timokau timokau merged commit 79989eb into NixOS:master Sep 22, 2019
13 checks passed
13 checks passed
Evaluation Performance Report Evaluator Performance Report
Details
grahamcofborg-eval ^.^!
Details
grahamcofborg-eval-check-maintainers matching changed paths to changed attrs...
Details
grahamcofborg-eval-check-meta config.nix: checkMeta = true
Details
grahamcofborg-eval-darwin nix-instantiate --arg nixpkgs { outPath=./.; revCount=999999; shortRev="ofborg"; } ./pkgs/top-level/release.nix -A darwin-tested
Details
grahamcofborg-eval-nixos nix-instantiate --arg nixpkgs { outPath=./.; revCount=999999; shortRev="ofborg"; } ./nixos/release-combined.nix -A tested
Details
grahamcofborg-eval-nixos-manual nix-instantiate --arg nixpkgs { outPath=./.; revCount=999999; shortRev="ofborg"; } ./nixos/release.nix -A manual
Details
grahamcofborg-eval-nixos-options nix-instantiate --arg nixpkgs { outPath=./.; revCount=999999; shortRev="ofborg"; } ./nixos/release.nix -A options
Details
grahamcofborg-eval-nixpkgs-manual nix-instantiate --arg nixpkgs { outPath=./.; revCount=999999; shortRev="ofborg"; } ./pkgs/top-level/release.nix -A manual
Details
grahamcofborg-eval-nixpkgs-tarball nix-instantiate --arg nixpkgs { outPath=./.; revCount=999999; shortRev="ofborg"; } ./pkgs/top-level/release.nix -A tarball
Details
grahamcofborg-eval-nixpkgs-unstable-jobset nix-instantiate --arg nixpkgs { outPath=./.; revCount=999999; shortRev="ofborg"; } ./pkgs/top-level/release.nix -A unstable
Details
grahamcofborg-eval-package-list nix-env -qa --json --file .
Details
grahamcofborg-eval-package-list-no-aliases nix-env -qa --json --file . --arg config { allowAliases = false; }
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.