14 Commits (52a17f0ddffebd1bc706652eab77356f66337e5f)

Author	SHA1	Message	Date
Alvar Penning	073ee0e4ab	umlet: 14.3.0 -> 15.0.0	2 years ago
Ben Siraphob	127733211e	treewide: unzip buildInputs to nativeBuildInputs (#112302)	3 years ago
Profpatsch	4a7f99d55d	treewide: with stdenv.lib; in meta -> with lib; ... Part of: https://github.com/NixOS/nixpkgs/issues/108938 meta = with stdenv.lib; is a widely used pattern. We want to slowly remove the `stdenv.lib` indirection and encourage people to use `lib` directly. Thus let’s start with the meta field. This used a rewriting script to mostly automatically replace all occurances of this pattern, and add the `lib` argument to the package header if it doesn’t exist yet. The script in its current form is available at https://cs.tvl.fyi/depot@2f807d7f141068d2d60676a89213eaa5353ca6e0/-/blob/users/Profpatsch/nixpkgs-rewriter/default.nix	3 years ago
Alvar Penning	0a53c6b565	maintainers: rename geistesk to oxzi ... For reasons I have renamed my GitHub account and would like to include this name change here.	4 years ago
Michael Reilly	84cf00f980	treewide: Per RFC45, remove all unquoted URLs	4 years ago
volth	46420bbaa3	treewide: name -> pname (easy cases) (#66585) ... treewide replacement of stdenv.mkDerivation rec { name = "*-${version}"; version = "*"; to pname	5 years ago
Jörg Thalheim	c8ff4a92f7	treewide: use runtimeShell instead of stdenv.shell whenever possible ... Whenever we create scripts that are installed to $out, we must use runtimeShell in order to get the shell that can be executed on the machine we create the package for. This is relevant for cross-compiling. The only use case for stdenv.shell are scripts that are executed as part of the build system. Usages in checkPhase are borderline however to decrease the likelyhood of people copying the wrong examples, I decided to use runtimeShell as well. (cherry picked from commit dadc7eb329)	5 years ago
Jörg Thalheim	dadc7eb329	treewide: use runtimeShell instead of stdenv.shell whenever possible ... Whenever we create scripts that are installed to $out, we must use runtimeShell in order to get the shell that can be executed on the machine we create the package for. This is relevant for cross-compiling. The only use case for stdenv.shell are scripts that are executed as part of the build system. Usages in checkPhase are borderline however to decrease the likelyhood of people copying the wrong examples, I decided to use runtimeShell as well.	5 years ago
geistesk	dfa5820a7c	umlet: 14.2 -> 14.3	6 years ago
davidak	3270aa896b	replace "Mac OS X" and "OS X" with "macOS" ... as it is the official name since 2016 https://en.wikipedia.org/wiki/Macintosh_operating_systems#Desktop exception are parts refering to older versions of macOS like "GUI support for Mac OS X 10.6 - 10.12. Note that Emacs 23 and later [...]"	7 years ago
Damien Cassou	58dc8e3024	Remove myself from maintainers	7 years ago
Damien Cassou	79f6563000	umlet: 13.3 -> 14.2	8 years ago
Damien Cassou	3dc24b9e53	umlet 13.2 → 13.3	9 years ago
Damien Cassou	d69c9bb42d	Umlet 13.1 -> 13.2	9 years ago
Damien Cassou	dcc2f1ac38	New package for Umlet 13.1	10 years ago