https://github.com/nix-community/nix-straight.el

Low-level Nix integration to straight.el [maintainer=@ckiee]
https://github.com/nix-community/nix-straight.el

Last synced: 3 months ago
JSON representation

Low-level Nix integration to straight.el [maintainer=@ckiee]

• Host: GitHub
• URL: https://github.com/nix-community/nix-straight.el
• Owner: nix-community
• License: mit
• Fork: true (vlaci/nix-straight.el)
• Created: 2021-12-10T23:36:22.000Z (almost 3 years ago)
• Default Branch: master
• Last Pushed: 2023-10-10T14:48:59.000Z (about 1 year ago)
• Last Synced: 2024-07-02T11:16:35.617Z (5 months ago)
• Language: Nix
• Homepage:
• Size: 22.5 KB
• Stars: 19
• Watchers: 3
• Forks: 11
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# nix-straight.el

Low-level Nix integration to [straight.el](https://github.com/raxod502/straight.el)

See [nix-doom-emacs](https://github.com/nix-community/nix-doom-emacs) for a usage example.

There are a couple of issues you may need to be aware of:

* Package names are dumbly inferred using the `meta.homepage` and `ename`

  attributes. If they are both present and not match, then the packages is

  instaled under both names in the `repos` directory.

* Packages are symlinked from the store so all VCS related operations are

  unavailable and package contents may differ from the ones would be installed

  from e.g. MELPA.

* Recipe targets are totally ignored, so there is currently no way of knowing if

  a derivation from melpa would be used instead of a fork for example. However I

  am planning to add a tool to generate Nix expressions from straight recipes in

  the future.