NixOS · schuelermine · Mar 12, 2022 · Mar 12, 2022 · Mar 13, 2022 · Mar 13, 2022
diff --git a/rfcs/0123-flake-names.md b/rfcs/0123-flake-names.md
@@ -0,0 +1,89 @@
+---
+feature: flake-names
+start-date: 2022-03-12
+author: Anselm Schüler
+co-authors: None
+shepherd-team: None
+shepherd-leader: None
+related-issues: None
+---
+
+# Summary
+[summary]: #summary
+
+Flakes can declare the field `name`.  
+It represents the name of the flake.  
+The derivations for a flake are no longer called `source`, but use the flake name.
+
+# Motivation
+[motivation]: #motivation
+
+Flake-centric workflows often end up with a lot of derivations named “source”, and it’s difficult to navigate this.
+This can also make flake-centric commands friendlier and easier to approach.
+
-
+- Unique names are useful for the purpose of finding duplicate things caused by diamond dependencies. (E.g. `a -> b -> d1`, `a -> c -> d2`. Without a unique name (`d`), it is not possible to correlate `d1` and `d2` reliably.)
+
-
+- Unique names are useful for the purpose of finding duplicate things caused by diamond dependencies. (E.g. `a -> b -> d1`, `a -> c -> d2`. Without a unique name (`d`), it is not possible to correlate `d1` and `d2` reliably.)
+
+# Detailed design
+[design]: #detailed-design
+
+A new supported property for flakes is introduced, `name`.  
+The derivation that contains the flake’s content is called `flake-source-${name}`  
+If a source control tag (e.g. git tag such as V3) is available, it is `flake-source-${name}-${tag}`.
+
+# Examples and Interactions
+[examples-and-interactions]: #examples-and-interactions
+
+Running `nix flake metadata` on a flake that declares this field displays it at the top.  
+Running `nix flake show` on a flake that declares this field shows the name instead of the URL, followed by the URL in parentheses.
+
+Examples:
+
+File `/example/flake.nix`
+```nix
+{
+  name = "example";
+  outputs = { ... }: {
+    lib.example = "example";
+  };
-  outputs = { ... }: {
-    lib.example = "example";
-  };
+  outputs = { self, ... }: {
+    lib.example = self.name;
+  };
-  outputs = { ... }: {
-    lib.example = "example";
-  };
+  outputs = { self, ... }: {
+    lib.example = self.name;
+  };
+}
+```
+
+Shell
+```console
+$ nix eval git+file:///example
+[…] copying flake-source-example
+"example"
+```
+
+Example of interactions:
+
+Shell (using the previous file)
+```
+$ nix flake metadata /example
+Name:          example
+Resolved URL:  git+file:///example
+Locked URL:    …
+$ nix flake show /example
+example (git+file:///home/anselmschueler/Code/example?rev=b0&rev=c714c8624f5d49a9d88e6e24550dd88515923c18)
+└───lib: unknown
+```
+
+# Drawbacks
+[drawbacks]: #drawbacks
+
+This may cause clutter and additional maintenance.  
+Since this changes the output of nix flake metadata and nix flake show, it might cause scripts that read this output to break.
+
+# Alternatives
+[alternatives]: #alternatives
+
+Flake names could be handled entirely through outside means, with things like the global registry merely pointing to flakes under names.
+
+# Unresolved questions
+[unresolved]: #unresolved-questions
+
+The name scheme could be changed. `flake-source-${name}` could be too long. Alternatives include `source-${name}`.  
+The interactions with nix flake metadata and nix flake show are not critical to the design, which is mostly aimed at clarifying derivation names.
+
+# Future work
+[future]: #future-work
+
+Flake usability can be improved.