* Initial nixos container commit because I want to view diffs between changes
* Updates / Improvements
* Note regarding static networking
* Updates
* update
* Update.
* Update.
* Update
Thanks Linus for the proof-read :)
* Update.
Mention that nixops container backend is also affected as pointed out by
fpletz.
* fixup! wording, spelling
* Move document according to assigned RFC number
* Linkify related issues
As it's done in https://github.com/NixOS/rfcs/blob/master/rfcs/0004-replace-unicode-quotes.md
* Bind-mounting Nix state isn't strictly needed
It's sufficient to have the store-paths available.
* Wording
Co-authored-by: Kevin Cox <kevincox@kevincox.ca>
* Clarify "default mode", remove a few unnecessary implementation details
* rfc108: add shepherds
Co-authored-by: Jörg Thalheim <Mic92@users.noreply.github.com>
* Apply wording suggestions from @lheckemann
Co-authored-by: Linus Heckemann <git@sphalerite.org>
* Usage of `nsenter` to update a container's configuration is not relevant for the RFC
* Rename `config` to `system-config` to avoid ambiguities in the module system
* Explicitly talk about deprecation of current implementation
Co-authored-by: Erik Arvstedt <erik.arvstedt@gmail.com>
Co-authored-by: Kevin Cox <kevincox@kevincox.ca>
Co-authored-by: Jörg Thalheim <Mic92@users.noreply.github.com>
Co-authored-by: Linus Heckemann <git@sphalerite.org>
* Initial draft "ret-cont" recursive Nix
* Fix typos and finish trailing sentance
* Switch to advocating temp store rather than daemon socket
Also:
- Allow fixed output builds (in that temp store)
- Clean up drawbacks and alternatives.
* ret-cont-recursive-nix: Fix typo
Thanks @siddharthist!
Co-Authored-By: Ericson2314 <git@JohnEricson.me>
* ret-cont-recursive-nix: Fix typo
Thanks @Mic92
Co-Authored-By: Ericson2314 <git@JohnEricson.me>
* ret-cont-recursive-nix: Fix typo
Thanks @globin
Co-Authored-By: Ericson2314 <git@JohnEricson.me>
* ret-cont-recursive-nix: Fix typo
Thanks @siddharthist!
Co-Authored-By: Ericson2314 <git@JohnEricson.me>
* ret-cont-recursive-nix: Clean up motivation, adding examples
* ret-cont-recursive-nix: Improve syntax highlighting
* Do a lousy job formalizing the detailed design
Break off some previously inline observations into their own subsection.
* ret-cont-recursive-nix: Mention `builtins.exec` in alternatives
* ret-cont-recursive-nix: Fix typo
Thanks @Mic92!
Co-Authored-By: Ericson2314 <git@JohnEricson.me>
* ret-cont-recursive-nix: Remove dangling "$o"
The later examples with `nix-instantiate` automatically get all the outputs of the final rewritten drv, so there's no output iteration needed. `"$o"` was mistakenly copied over from the earlier examples.
Thanks to @ocharles for asking me the question that led me to this. Hopefully this change answers that?
* Update rfcs/0000-ret-cont-recursive-nix.md
Co-Authored-By: Domen Kožar <domen@enlambda.com>
* ret-cont-recursive: Fix typo
about -> out
* ret-cont: Add examples and expand future work
* ret-cont: Fix syntax error
No `let`, so don't need `in`.
* ret-cont: Mention Ninja's upcomming `dyndep` and C++ oppertunity
* ret-cont: Fix missing explicit `outputs` and `__recursive`
This was in the "wrapper" derivation example.
* ret-cont: "caching builds" -> "caching evaluation"
We already cache builds just fine, thanks!
Thanks @globin for catching
* ret-cont: Improve formalism and reference #62
* drv-build-drv: Start drafting from old ret-cont-recursive-nix RFC
* drv-buiild-drv: WIP rewrite
* plan-dynamism: Rewrite RFC yet again
* plan-dynamism: Rename file accordingly
* plan-dynanism: Fix typo
Thanks @mweinelt.
* plan-dynanism: Fix formalism slightly
* Apply suggestions from code review
Thanks!
Co-authored-by: Rosario Pulella <Rosariopulella@gmail.com>
Co-authored-by: Ninjatrappeur <NinjaTrappeur@users.noreply.github.com>
* plan-dynamism: `Buildables` -> `DerivedPathsWithHints`
Thanks @sternenseemann for catching.
* plan-dynamism: Add semantics and examples for `!` syntax
* plan-dynamism: Too many dashes in `--derivation`
* plan-dynanism: Put pupose of text hashing before name
* Apply suggestions from code review
Co-authored-by: Ollie Charles <ollie@ocharles.org.uk>
* Apply suggestions from code review
Co-authored-by: Ollie Charles <ollie@ocharles.org.uk>
* Apply suggestions from code review
* Update rfcs/0000-plan-dynanism.md
* plan-dynanism: Fix bad sentence
Thanks @roberth!
* plan-dynamism: Number the two parts
* plan-dynamism: Rip out part 2
There is more to do I'm sure, but I wanted to get the ball rolling.
* plan-dynamism: New motivation
* plan-dynamism: Fix typo
Thanks @L-as
* TEMP PLES AMEND
* [RFC 0092] Rename file
* [RFC 0092] Fix YAML header
* [RFC 0092] Rewrite summary
* [RFC 0092] Add link to documentation
* [RFC 0092] Rewrite example section
* [RFC 0092] Small fix
* [RFC 0092] Rewrite drawbacks and alternatives
* [RFC 0092] Improve alternatives section
* [RFC 0092] Fix syntax error
* [RFC 0092] Small change
* [RFC 0092] Remove unnecessary file
* [RFC 0092] Add comment about IFD
* [RFC 0092] Fix typo
* Update rfcs/0092-plan-dynamism.md
Co-authored-by: Jörg Thalheim <Mic92@users.noreply.github.com>
* plan-dynamism-experiment: Make clear is experimental
* plan-dynamism-experiment: Fix typo
Thanks @L-as
Co-authored-by: Langston Barrett <langston.barrett@gmail.com>
Co-authored-by: Jörg Thalheim <Mic92@users.noreply.github.com>
Co-authored-by: Robin Gloster <mail@glob.in>
Co-authored-by: Domen Kožar <domen@enlambda.com>
Co-authored-by: Rosario Pulella <Rosariopulella@gmail.com>
Co-authored-by: Ninjatrappeur <NinjaTrappeur@users.noreply.github.com>
Co-authored-by: Ollie Charles <ollie@ocharles.org.uk>
Co-authored-by: Las Safin <me@las.rs>
Co-authored-by: Eelco Dolstra <edolstra@gmail.com>
* CAP RFC: First draft
* typo
* Apply @grahamc's suggestions
Co-Authored-By: Graham Christensen <graham@grahamc.com>
* nix code -> Nix expression
* Break-up the big introduction paragraph
As suggested in https://github.com/NixOS/rfcs/pull/62/files#r356694585
* Rename to match the PR number
* Rename the drv attribute to __contentAddressed
Makes it more in line with other "magic" attributes like
`__structuredAttributes`
Also fix the orthograph
* Mention the GC issue
* Remove the ambiguity on what an `output` is
* Replace aliases paths by a pathOf mapping
* Move the example after the design description
* Rephrase the design
In particular, replace `static` and `dynamic` by `symbolic` and
`resolved`
* Add shepherd team
* Rewrite the RFC to account for the RFC meeting comments
- Add the notion of `drvOutputId`
- Replace the alias paths by a `PathOf(drvOutputId)` function
- Mention the notion of "truster" in the `PathOf` function
* Add a section about leaking output paths
* Refine the design summary
* Rename dependency-addressed into input-addressed
And define the term at the begining of the RFC
* minor fixup after comments
* Apply suggestions from code review
Co-authored-by: asymmetric <lorenzo@mailbox.org>
Co-authored-by: Profpatsch <philip.patsch@tweag.io>
* Update rfcs/0062-content-addressed-paths.md
* Update the terminology to match the in the implementation
* Reword the detailed design presentation
* Quote some strings in the yaml frontmatter
* Add a design paragraph about the remote caching
And update the “unresolved questions” to take it into account
* Lift the determinism requirement
It's not required anymore by the current remote caching semantics
* Typo
Co-authored-by: davidak <davidak@users.noreply.github.com>
* Apply suggestions from code review
Co-authored-by: davidak <davidak@users.noreply.github.com>
* Rewrite the RFC
This is mostly a full-rewrite of the RFC to
1. Make it more “incremental”: A first part just describes the minimal
model upon which everything is based, and a second one shows
different extensions of this model to add more features
2. Remove the big ugly examples that don’t add much value because they
aren’t really readable
3. Add a python pseudo-code pseudo-formalisation of the RFC.
This is imho both more readable and precise than nested bullet-points
of handwaved language
* Make the python samples a bit more pythonic
Co-authored-by: zseri <zseri.devel@ytrizja.de>
* Explicit that unresolved dependencies are eval-time
* Prettify
* Make the end-goal an experiment
Simplify the paperwork and just get this to FCP because right now it’s stuck in a hole
Co-authored-by: Théophane Hufschmitt <regnat@users.noreply.github.com>
Co-authored-by: Graham Christensen <graham@grahamc.com>
Co-authored-by: John Ericson <John.Ericson@Obsidian.Systems>
Co-authored-by: asymmetric <lorenzo@mailbox.org>
Co-authored-by: Profpatsch <philip.patsch@tweag.io>
Co-authored-by: Jörg Thalheim <Mic92@users.noreply.github.com>
Co-authored-by: Eelco Dolstra <edolstra@gmail.com>
Co-authored-by: davidak <davidak@users.noreply.github.com>
Co-authored-by: zseri <zseri.devel@ytrizja.de>
* Switch to CommonMark for documentation
This RFC proposes to convert the documentation for the Nix, Nixpkgs
and NixOS projects from Docbook to CommonMark Markdown. It proposes
requirements for web facing documentation. It does not mandate
a choice of toolchain to generate a website with documentation. The
choice is left to the implementers and maintainers.
* Update rfcs/0000-commonmark-docs.md
Co-authored-by: Profpatsch <mail@profpatsch.de>
* Update rfcs/0000-commonmark-docs.md
Co-authored-by: Frederik Rietdijk <freddyrietdijk@fridh.nl>
* Update rfcs/0000-commonmark-docs.md
Co-authored-by: davidak <davidak@users.noreply.github.com>
* Update rfcs/0000-commonmark-docs.md
Co-authored-by: davidak <davidak@users.noreply.github.com>
* Update rfcs/0000-commonmark-docs.md
Co-authored-by: Ryan Mulligan <ryan@ryantm.com>
* Add shepherd metadata
* Add shepherd metadata
* Allow CommonMark plus small number of extensions
The exact set of extensions used is left to the documentation team.
* Final adjustments
- Nix now already uses markdown
- Fix grammar mistake
- Remove requirement of extensions having to be supported by
at least 3 toolchains
- Add requirement for an extension for references
- Rename the file to its designated name
Co-authored-by: Profpatsch <mail@profpatsch.de>
Co-authored-by: Frederik Rietdijk <freddyrietdijk@fridh.nl>
Co-authored-by: davidak <davidak@users.noreply.github.com>
Co-authored-by: zimbatm <zimbatm@zimbatm.com>
Co-authored-by: Ryan Mulligan <ryan@ryantm.com>
Co-authored-by: Linus Heckemann <git@sphalerite.org>
Co-authored-by: Silvan Mosberger <contact@infinisil.com>
* Expand the RFC acronym at least once
While it is probably know to most it should also be documented what we expand RFC to.
* Capitalize "RFC"
Co-authored-by: zimbatm <zimbatm@zimbatm.com>
Co-authored-by: Eelco Dolstra <edolstra@gmail.com>
Co-authored-by: zimbatm <zimbatm@zimbatm.com>
* A small RFC on deprecating URL syntax
* Convert alternatives to a list
* Add a mention of tooling in future work
* A remark from @globin about one more problem with unquoted URLs
* Grammar edit: comparison of URLs, paths and strings.
Co-Authored-By: 7c6f434c <7c6f434c@mail.ru>
* Style edit: possibility of future removal
Co-Authored-By: 7c6f434c <7c6f434c@mail.ru>
* 0045: commit to using the tooling that now exists
* Update rfcs/0045-deprecate-url-syntax.md
Shepherd team
Co-Authored-By: Domen Kožar <domen@enlambda.com>
* Fix shepherd list
* Update based on a discussion
* Explicitly make future removal conditional on editions; restrict the claim about no special support to the Nix language itself
This paragraph seems to be a leftover or copy-pasta from the RFC template. It doesn't really fit into the flow of the text, so I think it was included or left here by mistake.
* rfc51: close stale issues initial draft
* rfc0051: use staleLabel consistent with nixpkgs labeling conventions
* rfc0051: do not close issues
* rfc0051: reword motivation
* record the members of the shepherd team
* Update rfcs/0051-mark-stale-issues.md
Co-Authored-By: asymmetric <lorenzo@mailbox.org>
* [RFC 0051] remove references to "issue" in stale message
* 0036-rfc-process-team-amendment: draft
Co-authored-by: Graham Christensen <graham@grahamc.com>
* 0036-rfc-process-team-amendment: clarifications
Co-Authored-By: globin <mail@glob.in>
* 0036-rfc-process-team-amendment: remove typo recommendation
The github UI has improved since this was written and we should no
longer discourage this.
* 0036-rfc-process-team-amendment: Glossary -> Terminology
* 0036-rfc-process-team-amendment: disallow author/co-author as Shepherds
* 0036-rfc-process-team-amendment: incorporate feedback from discussion
* 0036-rfc-process-team-amendment: update rfc process graph
* 0036-rfc-process-team-amendment: merge postpone and reject
* 0036-rfc-process-team-amendment: improve Shepherd Leader paragraph
* copy rfc template, unnumbered as of yet
* musl-libc RFC: first draft
* musl-libc RFC: rename to patch pull req number
* musl-libc: whoops, no links in top bit, that's metadata.
Move links to later.
* record the name of a brave co-author
* musl rfc: squash second batch of changes
* rfc: specify initial team \o/, add a small clarification.
* Add myself to the "musl team"
