If you are wondering where the data of this site comes from, please visit GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

benley/bazel_rules_pex 34

Python PEX rules for Bazel

benley/aurora-jobhopper 21

Handy http redirect service for Apache Aurora jobs

benley/aurora-jsonnet 9

Examples: jsonnet as a config language for Apache Aurora

benley/chef-aurora 7

Chef cookbook for Apache Aurora

benley/arsenic 3

parser/compiler for knitting patterns

benley/aurora 2

Apache Aurora

benley/chef-nix-multiuser 2

Chef cookbook to deploy Nix with nix-daemon

benley/bazel_rules_haskell 1

Haskell rules for Bazel

benley/butcher 1

(obsolete) General purpose build system for projects spanning many source repos

benley/distroless 1

🥑 Language focused docker images, minus the operating system.



started time in a day


started time in 2 days


started time in 2 days


started time in 2 days


started time in 3 days

created repositoryxtruder/docker-images

Just a bunch of docker images, that don't have other place to be

created time in 3 days

pull request commentNixOS/rfcs

[RFC 0085] ZHF on master, set release freeze dates

also cc @alyssais @Ericson2314 if you want to attend.


comment created time in 3 days

pull request commentNixOS/rfcs

[RFC 0085] ZHF on master, set release freeze dates

I've set up a meeting availability webpage:

@andir @jonringer @garbas @mic92 Can you please fill it out?


comment created time in 3 days

pull request commentNixOS/rfcs

[RFC 0075]: Declarative wrappers

Thanks @doronbehar for the work! @FRidh @edolstra shall we have a look over it and arrange a new meeting?


comment created time in 3 days


started time in 3 days

fork ayust/certbot

Certbot is EFF's tool to obtain certs from Let's Encrypt and (optionally) auto-enable HTTPS on your server. It can also act as a client for any other CA that uses the ACME protocol.

fork in 3 days


started time in 3 days


started time in 3 days

pull request commentNixOS/rfcs

[RFC 0081] Show unmaintained packages

lets plan another date:


comment created time in 4 days


started time in 4 days



started time in 4 days


started time in 5 days


started time in 5 days

pull request commentNixOS/rfcs

[RFC 0035] Default `name` from `pname`

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:


comment created time in 5 days

created repositoryemilypi/graded-functors

Graded semigroupds, monoids, and groups

created time in 5 days

pull request commentNixOS/rfcs

[RFC 0005] Nix encryption



comment created time in 6 days


started time in 7 days

PR closed NixOS/rfcs

[RFC 0086] NixOS generation APIs
+185 -0


1 changed file


pr closed time in 8 days

Pull request review commentNixOS/rfcs

[RFC 0083] common interface package sets

+---+feature: common-interface-package-sets+start-date: 2020-12-19+author: Frederik Rietdijk (@FRidh)+co-authors:+related-issues:+---++# Summary+[summary]: #summary++The Nixpkgs package set consists of a large amount of packages of which a+significant amount of grouped into sub package sets. This RFC recommends a+common interface for these package sets.++# Motivation+[motivation]: #motivation++The Nixpkgs package set consists of a large amount of packages of which a+significant amount of grouped into sub package sets. Sets exist for various+languages, frameworks and plugins.++They are typically grouped together for one of the following two reasons:+- clarity, e.g. because they're written in the same language or framework;+- necessity, e.g. for compatibility reasons.++Over time different methods for defining package sets were created. Currently+multiple methods are in use in Nixpkgs and pull requests are opened to modify+sub package sets interfaces from one kind to another. Not only is this confusing+for users but it also causes trouble; in some cases overriding of derivations+inside a set is not possible or cross-compilation is broken.++This RFC thus aims to unify the package sets to a common interface for the+following reasons:+- simplify usage of package sets and reduce confusion surrounding them;+- single approach for dealing with overrides;+- handle variants of a package set;+- ensure cross-compilation works.++Often one also wants to build an environment with an interpreter or main program+and some additional packages or plugins. This RFC will therefore also recommend+a function each package set should offer for doing so, when appliceable that is.++## Related issues++TODO: refer to these issues in correct place.++- Common override interface derivations Make PHP packages overrideable Change in emacs interface Package set for Octave Python package set is not overrideable+ Support `overrideScope'` in Python package set+ Common `overrideArgs` for sub package sets+ May be resolved using+  `overrideAuto` in Detailed design+[design]: #detailed-design++We will now look in more detail at what a common interface should offer.++## Attribute name of the package set: `fooPackages` versus `foo.pkgs`++Two different interfaces are common in Nixpkgs when referring to package sets:+- `fooPackages`+- `foo.pkgs`++TODO which one to pick? Consider also overriding of the interpreter or main program and how that should propagate. Consider also the function for generating variants, where you need to have a name under which your interpreter or main program is available in the subpackage set.+## Variants+Often multiple variants of a package set need to be created. E.g., in case of+emacs or Python there are different versions of the program and each of them+should have their own package set. For this reason it is important that one can+easily create a new variant++```nix+fooPackagesFor = foo: import ./foo-packages.nix { ... };+fooPackages_3_6 = fooPackagesFor foo_3_6;+```++## Set overriding+It should be possible to override packages in a sub package set and have the+other packages in the set take that override into account. To that end, a scope+is created++```nix+lib.makeScope pkgs.newScope (self: with self; {+  ...+}+```++that can be overridden using `overrideScope'`++```nix+fooPackages_3_6.overrideScope' overrides;+```++where `overrides` is of the form++```nix+(final: previous: { ... })+```++In case one uses overlays with Nixpkgs, one could now make the overrides+composible using++```nix+fooPackages_3_6 = fooPackages_3_6.overrideScope' overrides;+```++## Package overriding++Now that it is possible to override a set, a common interface to overriding the+packages inside the set is needed as well. This is treated in [RFC+67]( Cross-compilation++For cross-compilation it is important that `callPackage` in the sub package set+has access to the spliced versions of the sub package set. Until recently, there+were no spliced sub package sets in Nixpkgs, but support was added for Python+utilizing the `makeScopeWithSplicing` function. There is [room for+improvement]( important aspect for making this work is that, when constructing the package+set, it needs to know its own top-level attribute.

Referring to the incorrect set


comment created time in 8 days


started time in 9 days


started time in 9 days


started time in 9 days