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

sublime-merge: init at 1107 #58994

Merged
merged 3 commits into from Apr 24, 2019
Merged

Conversation

zookatron
Copy link
Contributor

@zookatron zookatron commented Apr 5, 2019

Motivation for this change
Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • 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)
  • Assured whether relevant documentation is up to date
  • Fits CONTRIBUTING.md.

Copy link
Contributor

@worldofpeace worldofpeace left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, left a few comments.

Also you should add yourself to the maintainers list in a separate commit like

maintainers: add zookatron

and before the package init

@zookatron
Copy link
Contributor Author

Hi @tadeokondrak @worldofpeace ! I've applied all the requested changes in the recent updates to my branch. Let me know if there's anything else that can be improved!

Copy link
Contributor

@worldofpeace worldofpeace left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything builds and executes fine.

@worldofpeace worldofpeace mentioned this pull request Apr 6, 2019
9 tasks
@worldofpeace
Copy link
Contributor

ping @jtojnar @Mic92 because you reviewed #47378

@jtojnar
Copy link
Contributor

jtojnar commented Apr 6, 2019

It might make sense to change the sublime3’s common.nix to make it reusable. After all they both use the same base.

@zookatron
Copy link
Contributor Author

It might make sense to change the sublime3’s common.nix to make it reusable. After all they both use the same base.

Possibly, I don't have enough experience to comment on how nixos commonly does that, but it seems to be that there's enough differences between the sublime3 derivation and the sublime-merge derivation to not really make it worth it. They definitely share a few important bits of logic like the pkexec fixes, but sublime-merge is missing a lot of things that sublime3 does like supporting 32 bit systems, wrapping the plugin_host, creating a custom sublime_bash and fixing the Packages to use it, etc. Seems to me like you would need enough conditionals and overrides to account for the differences that it would just make the packages more difficult to maintain properly overall, but I don't know.

@zookatron
Copy link
Contributor Author

@jtojnar Are there any blockers to having this merged? Would you like me to work on creating the shared common.nix file before we commit this? I'm happy to help if that's what you think needs to happen.

@jtojnar
Copy link
Contributor

jtojnar commented Apr 10, 2019

Factoring out Sublime packages into a common expression can wait to future pull requests. However, I would like to see all the non-Merge-specific deviations from the Text expression to be applied there as well, in order to make the future unification easier. Basically, we want a minimal git diff --no-index pkgs/applications/editors/sublime/3/common.nix pkgs/applications/version-management/sublime-merge/common.nix.

@zookatron
Copy link
Contributor Author

Factoring out Sublime packages into a common expression can wait to future pull requests. However, I would like to see all the non-Merge-specific deviations from the Text expression to be applied there as well, in order to make the future unification easier. Basically, we want a minimal git diff --no-index pkgs/applications/editors/sublime/3/common.nix pkgs/applications/version-management/sublime-merge/common.nix.

@jtojnar I've added a commit that updates the sublime3 and sublime-merge common.nix files to better reflect their shared structure. If you run git diff --no-index pkgs/applications/editors/sublime/3/common.nix pkgs/applications/version-management/sublime-merge/common.nix it now has a minimal set of diffs that more accurately reflects the necessary build differences between the two packages. Incidentally this also fixes a bug in sublime3 where the icon files where not being linked to the proper directory preventing the desktop environment from displaying their custom icons.

In the future it's desired to unify Sublime packages expressions.
So them having a shared structure will make this more achievable.
@worldofpeace
Copy link
Contributor

Sorry that I didn't merge that for you sooner @zookatron

Thank you for your contribution and co-operation 💖

@zookatron
Copy link
Contributor Author

No problem, thanks @worldofpeace!

@zookatron zookatron deleted the sublime-merge branch April 25, 2019 03:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants