I think the idea of NixOS is great and I would like to contribute to the project. First I will try to submit a first nixpkg and maintain it. It is an emacsPackage.
I’m not an expert in emacs packaging, but first it depends what you mean to “test” your package. Are you testing your derivation directly, or the integration of this derivation into nixpkgs? If you just want to test the derivation, you don’t need any copy of nixpkgs, you should be able to just call your package with epkgs.callPackage ./default.nix {}, with something like:
If you want to integrate it in nixpkgs, and if the package is not present in elpa/melpa, then you can add it in the list in pkgs/applications/editors/emacs/elisp-packages/manual-packages.nix with something like:
# …
# make sure to move your default.nix in pkgs/applications/editors/emacs/elisp-packages/lsp-bridge/default.nix
lsp-bridge = callPackage ./lsp-bridge {};
# …
Then, it should appear as any other package I guess (but I’ve not tested), using something like:
Sure, feel free to edit the wiki if something is unclear. Note that you might want to edit the emac specific page in Emacs - NixOS Wiki
PS: to help people to quickly see that the issue is solved (this way they can only open non-solved issues), it’s a good idea to mark the solution as a solution.
edit ahah the solution button is different from the like button ^^ You can put only one solution, which will be reported appropriately when searching unsolved packages, unlike likes. But nevermind ^^