3 ms·
So basically, one could make this compatible with current Arch packages by making packages install into /nix/store/<id> instead?
by Svenstaro 11y ago
So basically, one could make this compatible with current Arch packages by making packages install into /nix/store/<id> instead?
- gosub 11y agoI don't know if a mechical/automatic process is possible, but it works for haskell and python packages from Hackage and PyPI. nix packages are not exactly packages, as in rpm or deb files, they are expressions in a functional language (think build recipes). there is a central repository of recipes on github: https://github.com/NixOS/nixpkgs/tree/master/pkgs https://github.com/NixOS/nixpkgs/tree/master/pkgs but you can make your own, and eventually make a pull request. They are more similar to Arch's PKGBUILDs. Packages in the central repository are constantly built by a continuos built process (http://nixos.org/hydra/ http://nixos.org/hydra/), that works both as a binary cache and as a testing system. This is an expression I wrote to install SuperCollider plugins https://gist.github.com/gosub/a42e265ec38d9df203d6 https://gist.github.com/gosub/a42e265ec38d9df203d6 using the Arch PKGBUILD as a reference https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=sc3-plugins-git https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=sc3-p...
- Ericson2314 11y agoYeah we package a lot of stuff these days---more than our market share would lead one to guess. So yes feel free to file a PR for anything missing, but there's no need to port Arch packages en masse.