about summary refs log tree commit diff
path: root/doc
AgeCommit message (Collapse)AuthorFilesLines
2023-02-07doc/contributing: remove last references to nameSandro Jäckel1-2/+2
pname+version should be used everywhere, so lets clean this up
2023-02-07add docs for makeSetupHookArtturin2-0/+38
2023-02-07Merge pull request #215121 from ncfavier/doc-gitignoreValentin Gagarin1-2/+1
2023-02-07Merge pull request #215114 from ncfavier/fixup-212642Valentin Gagarin1-2/+3
2023-02-07doc: use `gitignoreSource`Naïm Favier1-2/+1
Running `make -C doc` to build the manual locally leaves .xml artifacts in the tree. These are ignored by git, but they still get included in the build when not using flakes, which causes the corresponding chapters not to be built.
2023-02-07doc/stdenv: fixup #212642Naïm Favier1-2/+3
2023-02-06Merge pull request #214304 from obsidiansystems/pkg-config-metaJohn Ericson1-3/+45
meta.pkgConfigModules: Init convention
2023-02-06Merge pull request #214612 from stephank/feat/swift-docsDomen Kožar2-0/+177
doc: add section on swift
2023-02-06treewide: fix backwards smart apostrophesJason Yundt1-2/+2
According to the Unicode Standard, you should use U+2019 RIGHT SINGLE QUOTATION MARK for apostrophes [1]. Before this change, some of the text in this repo would use U+2018 LEFT SINGLE QUOTATION MARKs instead. [1]: https://www.unicode.org/versions/Unicode15.0.0/ch06.pdf#G12411
2023-02-05Merge pull request #214763 from lheckemann/doc-requirefileLinus Heckemann1-0/+27
fetchers: document requireFile
2023-02-05fetchers: document requireFileLinus Heckemann1-0/+27
2023-02-04doc: add section on swiftStéphan Kochen2-0/+177
2023-02-03meta.pkgConfigModules: Init conventionJohn Ericson1-3/+45
See docs. Follow-up work: - Existing packages should be converted - `defaultPkgConfigPackages` should assert on `meta.pkgConfigModules` and let `tests.pkg-config` alone test the build results. CC @sternenseemann Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
2023-02-01nixos/doc: fix typo in python.section.mdAndré Schröder1-1/+1
2023-01-31Merge master into staging-nextgithub-actions[bot]1-9/+5
2023-01-30Merge pull request #212684 from pennae/nixos-render-docspennae1-9/+5
nixos-render-docs: init, use for some manual rendering to docbook
2023-01-30Merge master into staging-nextgithub-actions[bot]3-0/+23
2023-01-30Merge pull request #212282 from hercules-ci/pkg-config-packagesRobert Hensing3-0/+23
defaultPkgConfigPackages: init
2023-01-30testers.hasPkgConfigModule: Extract and add tests, docsRobert Hensing1-0/+13
2023-01-29Merge master into staging-nextgithub-actions[bot]1-1/+5
2023-01-29Merge pull request #208793 from hadilq/androidenv/cmdline-tools-and-patcherArtturi1-1/+5
androidenv: Implement cmdline-tools and patcher
2023-01-29pkg-configPackages -> defaultPkgConfigPackagesRobert Hensing1-1/+1
This better reflects the purpose of the package set, while leaving room for a fancier, more complete implementation of the concept, with a nicer name.
2023-01-29doc: Add pkg-config sectionRobert Hensing2-0/+10
2023-01-29Merge master into staging-nextgithub-actions[bot]1-3/+3
2023-01-28doc/python: fix attr name for unittestCheckHook flagsNoah Fontes1-3/+3
The name should end in Array per the current conventions. This change also contains some minor formatting fixes, as the heading levels were inconsistent.
2023-01-27androidenv: Implement cmdline-tools and patcherHadi1-1/+5
- Replace cmdline-tools with tools because tools is obsolete now. - Depend emulator package to systemImages androidenv: fix issues on the PR androidenv: reformat androidenv: support excluding of `tools` package androidenv: provide `tools`, and `build-tools`, dependencies androidenv: replace includeTools with toolsVersion androidenv: fix a typo androidenv: add tests to check licenses and installed packages androidenv: check if tests are running! this commit should fail! androidenv: fix problems in the review https://github.com/NixOS/nixpkgs/pull/208793 androidenv: add test-suite to handle more tests around androidenv: fix the test after couldn't running them with ofborg Update pkgs/development/mobile/androidenv/build-tools.nix Co-authored-by: Sandro <sandro.jaeckel@gmail.com> androidenv: Resolving https://github.com/NixOS/nixpkgs/pull/208793#discussion_r1065851539 Update pkgs/development/mobile/androidenv/cmdline-tools.nix Co-authored-by: Sandro <sandro.jaeckel@gmail.com> Update pkgs/development/mobile/androidenv/tools.nix Co-authored-by: Sandro <sandro.jaeckel@gmail.com> androidenv: fix a typo
2023-01-27Merge remote-tracking branch 'origin/master' into staging-nextMartin Weinelt2-1/+6
2023-01-27Merge pull request #205646 from symphorien/ocamlconflictGuillaume Girol1-0/+5
ocamlPackages.findlib: detect conflicts of version early
2023-01-27nixos/manual: render module chapters with nixos-render-docspennae1-9/+5
this converts meta.doc into an md pointer, not an xml pointer. since we no longer need xml for manual chapters we can also remove support for manual chapters from md-to-db.sh since pandoc converts smart quotes to docbook quote elements and our nixos-render-docs does not we lose this distinction in the rendered output. that's probably not that bad, our stylesheet didn't make use of this anyway (and pre-23.05 versions of the chapters didn't use quote elements either). also updates the nixpkgs manual to clarify that option docs support all extensions (although it doesn't support headings at all, so heading anchors don't work by extension).
2023-01-26fix: doc typoMatthew Kenigsberg1-1/+1
2023-01-26Merge master into staging-nextgithub-actions[bot]1-2/+2
2023-01-26Merge pull request #212642 from ncfavier/doc-check-phaseNaïm Favier1-2/+2
2023-01-25doc/stdenv: clarify default check targetNaïm Favier1-2/+2
2023-01-25Merge master into staging-nextgithub-actions[bot]1-0/+6
2023-01-25postgresqlTestHook: run postgresqlTestSetupPost hook after setting upNick Cao1-0/+6
2023-01-24Merge master into staging-nextgithub-actions[bot]3-5/+5
2023-01-24doc: fix broken linksNaïm Favier3-5/+5
2023-01-24Merge branch 'master' into staging-nextVladimír Čunát1-3/+3
Trivial conflict in release notes, except that the xml/docbook parts are horrible for (semi-)automatic conflict resolution. Fortunately that's generated anyway.
2023-01-23dotnet-sdk_5: remove packagemdarocha1-3/+3
It's EOL and not used in nixpkgs anymore
2023-01-23Merge master into staging-nextgithub-actions[bot]1-1/+1
2023-01-22doc/langauge-frameworks/beam: fix broken link to `elixir-ls`Noah Snelson1-1/+1
2023-01-22Merge master into staging-nextgithub-actions[bot]1-1/+4
2023-01-21doc/manpage-urls.json: add gnunet.confNaïm Favier1-0/+1
2023-01-21doc/manpage-urls.json: add mpdNaïm Favier1-1/+3
2023-01-21doc: adapt to nativeCheckInputsGuillaume Girol3-15/+23
2023-01-21Merge branch 'nativeCheckInputs' into staging-nativeCheckInputsGuillaume Girol5-35/+43
2023-01-20cross-compilation.chapter.md: correct doCheck conditionalArtturin1-1/+1
2023-01-19Merge pull request #211082 from hercules-ci/fix-issue-16182Robert Hensing1-1/+1
Fix issue 16182 `Error: _assignFirst found no valid variant!`
2023-01-18doc/haskell: nitsDominik Schrempf1-19/+19
These are some suggested changes to the new documentation of Haskell in the Nixpkgs manual. They cover sections until, but excluding, the section "Available package versions". I am not an English native speaker, so please correct me and savage these changes! Also, please let me know if the suggestions are welcome, then I will continue with the next chapter.
2023-01-16multi-outputs.sh: Improve _assignFirst error messageRobert Hensing1-1/+1
Closes #16182 This improves the error message Error: _assignFirst found no valid variant! which occurred when the set of outputs was not sufficient to set the various outputDev, outputBin, etc variables. Specifically, this would mean that "out" is not among the outputs, which is valid for a derivation. This changes the message to something like error: _assignFirst: could not find a non-empty variable to assign to outputDev. The following variables were all unset or empty: dev out. If you did not define an "out" output, make sure to define all the specific required outputs: define an output for one of the unset variables. While this isn't a full explanation of what stdenv can and can not do, I think it's vast improvement over the 0 bits of information that it used to provide. This at least gives a clue as to what's going on, and even suggests a fix, although probably multiple such fixes are required in an instance where someone starts with a no-out derivation from scratch (and decide to persist).