about summary refs log tree commit diff
path: root/pkgs/servers/mesos-dns
AgeCommit message (Collapse)AuthorFilesLines
2024-03-29mesos-dns: 0.1.2 -> 0.9.0Aaron Jheng2-115/+20
2024-03-19treewide: add meta.mainProgram to packages with a single binarystuebinm1-0/+1
The nixpkgs-unstable channel's programs.sqlite was used to identify packages producing exactly one binary, and these automatically added to their package definitions wherever possible.
2020-07-31buildGoPackage packages: editorconfig fixeszowoq1-1/+1
2019-08-15treewide: name -> pname (easy cases) (#66585)volth1-1/+1
treewide replacement of stdenv.mkDerivation rec { name = "*-${version}"; version = "*"; to pname
2018-07-21pkgs/*: remove unreferenced function argumentsvolth1-1/+1
2016-09-16buildGoPackage: deps.json -> deps.nix in NIXONKamil Chmielewski3-102/+102
https://github.com/NixOS/nixpkgs/pull/17254#issuecomment-245295541 * update docs to describe `deps.nix` * include goDeps in nix-shell GOPATH * NixOS 16.09 rel notes about replacing goPackages
2016-08-11buildGoPackage: remove Go deps file `libs.json`Kamil Chmielewski1-16/+99
After #16017 there were a lot of comments saying that `nix` would be better than `JSON` for Go packages dependency sets. As said in https://github.com/NixOS/nixpkgs/pull/16017#issuecomment-229624046 > Because of the content-addressable store, if two programs have the > same dependency it will already result in the same derivation in > the > store. Git also has compression in the pack files so it won't make > much difference to duplicate the dependencies on disk. And finally > most users will just use the binary builds so it won't make any > differences to them. This PR removes `libs.json` file and puts all package dependencies in theirs `deps.json`.
2016-06-09Moving from fetchgit generated by go2nix to fetchFromGitHub where rev isKamil Chmielewski1-3/+4
a tag
2016-06-09no more goPackagesKamil Chmielewski1-4/+1
2016-06-09mesos-dns: extracted from goPackagesKamil Chmielewski2-0/+41