about summary refs log tree commit diff
path: root/doc/manual.xml
AgeCommit message (Collapse)AuthorFilesLines
2022-04-22doc: move testers to their own chapterArtturin1-0/+1
2022-04-16postgresqlTestHook: initRobert Hensing1-0/+1
2021-04-23doc/using: convert to markdownfricklerhandwerk1-3/+3
2021-04-23doc/contributing/*.xml: Convert to markdownBobby Rong1-4/+4
2021-03-19Merge pull request #116459 from Pamplemousse/document_vulnerability_roundupChristian Kauhaus1-0/+1
documentation: Add content about Vulnerability roundups
2021-03-17documentation: Add content about Vulnerability roundupsPamplemousse1-0/+1
Signed-off-by: Pamplemousse <xav.maso@gmail.com>
2021-03-14doc: Port stdenv to MarkdownJan Tojnar1-1/+1
Added the following ids to avoid possible id conflicts from ids auto-generated from titles: - setup-hook-perl - setup-hook-python - setup-hook-pkg-config - setup-hook-automake - setup-hook-autoconf - setup-hook-libxml2 - setup-hook-gdk-pixbuf
2021-03-14doc: Port stdenv/multiple-output to MarkdownJan Tojnar1-1/+1
2021-03-14doc: Port stdenv/meta to MarkdownJan Tojnar1-1/+1
2021-02-21doc/stdenv/platform-notes: convert to markdownBen Siraphob1-1/+1
2020-12-17Convert fetchers from DocBook to CommonMarkAndersonTorres1-1/+1
2020-12-17Convert trivial-builders from DocBook to CommonMarkAndersonTorres1-1/+1
2020-12-13doc/stdenv/cross-compilation: convert to markdownBen Siraphob1-1/+1
2020-12-05doc: Rename submitting-changes to chapterJan Tojnar1-1/+1
2020-09-24doc: rename guide to 'Nixpkgs Manual'Arnout Engelen1-1/+1
For consistency with 'NixOS Manual' and 'Nix Manual', to better match what it's often called in practice, and to match its URL and HTML title.
2019-10-30nixpkgs manual: move builders into one folderFrederik Rietdijk1-1/+1
2019-10-30nixpkgs manual: move using chapters into one folderFrederik Rietdijk1-3/+3
2019-10-30nixpkgs manual: move stdenv chapters into one folderFrederik Rietdijk1-5/+5
2019-10-30nixpkgs manual: move contributing chapters into one folderFrederik Rietdijk1-5/+5
2019-10-30nixpkgs manual: various improvements in introductionFrederik Rietdijk1-1/+1
- rename to preface to be inline with NixOS manual - refer to other manuals - use https - change example channel to 19.09
2019-10-21doc: move fhs and mkShell under builders/specialFrederik Rietdijk1-0/+1
In my opinion Functions should only contain pure functions. These are both meant to provide derivations so I put them under Builders. Don't know exactly *where* to put them so "special" it is...
2019-10-21doc: move overrides into separate chapterFrederik Rietdijk1-0/+1
2019-10-21doc: move image builders into new images chapterFrederik Rietdijk1-0/+1
2019-10-20doc: move fetchers and trivial builders under buildersFrederik Rietdijk1-1/+3
2019-10-20doc: split packages part into xml file per packageFrederik Rietdijk1-1/+1
2019-10-20doc: merge package notes and package-specific notesFrederik Rietdijk1-1/+0
Maybe there was an idea behind this separation, but looking at the contents I don't see any reason for these being separate.
2019-10-20doc: organize chapters into parts, and reduce toc depthFrederik Rietdijk1-16/+28
Reorganize the chapters into parts and reduce the TOC depth to make the TOC useful again. The top-level TOC is very brief, but that is fine because every part will have its own TOC. Section titles of languages/frameworks are also simplified to just the name of the language/framework.
2019-05-22[RFC] manual: rename to users and contributors manual, add some user notes ↵Michael Raskin1-1/+2
… (#60682) * manual: rename to users and contributors manual, add some user notes that should be there but don't fit in any chapter * manual: move the package notes that are completely usage-related to the upper user notes section * manual: link to package-specific development notes from user notes
2018-05-01nixpkgs docs: format =)Graham Christensen1-26/+21
2018-03-25Move all nixpkgs doc files in to the doc directoryGraham Christensen1-1/+1
This makes a makefile-driven developer workflow nicer.
2017-11-01docs: add section on common darwin issuesDaiderd Jordan1-0/+1
2017-01-24nixpkgs docs: Cross compilation docsJohn Ericson1-0/+1
2017-01-16Add overlays mechanism to Nixpkgs.Nicolas B. Pierron1-0/+1
This patch add a new argument to Nixpkgs default expression named "overlays". By default, the value of the argument is either taken from the environment variable `NIXPKGS_OVERLAYS`, or from the directory `~/.nixpkgs/overlays/`. If the environment variable does not name a valid directory then this mechanism would fallback on the home directory. If the home directory does not exists it will fallback on an empty list of overlays. The overlays directory should contain the list of extra Nixpkgs stages which would be used to extend the content of Nixpkgs, with additional set of packages. The overlays, i-e directory, files, symbolic links are used in alphabetical order. The simplest overlay which extends Nixpkgs with nothing looks like: ```nix self: super: { } ``` More refined overlays can use `super` as the basis for building new packages, and `self` as a way to query the final result of the fix-point. An example of overlay which extends Nixpkgs with a small set of packages can be found at: https://github.com/nbp/nixpkgs-mozilla/blob/nixpkgs-overlay/moz-overlay.nix To use this file, checkout the repository and add a symbolic link to the `moz-overlay.nix` file in `~/.nixpkgs/overlays` directory.
2016-11-22manual: reviewing contributions nixos -> nixpkgs (#20626)Eric Sagnes1-0/+1
2016-05-22nixpkgs manual: cleanup (#15611)Eric Sagnes1-2/+0
2016-04-23beam-support: update registry to latest '59b836d'Eric Merritt1-1/+1
2016-04-07nixpkgs manual: add multiple-output chapterVladimír Čunát1-0/+1
2016-01-15erlang support: Add minimal documentation to nixEric Merritt1-0/+1
This commit adds some very minimial documentation to the Nix manual. Hopefully, its enough to get someone started and serve as a first footstep for future documentation writers
2015-12-19nixpkgs manual: split languages into separate filesVladimír Čunát1-1/+1
There's no change in content except for amending the title of the section to mention "frameworks", as e.g. I don't consider Qt a language, and it's likely there will be more of similar cases in future. To be certain, I checked diff of the generated HTMLs.
2015-12-18Fixed a syntax error in the buildFHSChrootEnv example. Also, fixed the ↵Avery Glitch1-1/+1
manual.xml so it actually builds.
2015-07-12Move the submitting-changes down, after coding conventionsCillian de Róiste1-1/+1
2015-07-12Move the details from CONTRIBUTING.md to the manual #8734Cillian de Róiste1-0/+1
2015-06-30doc: make it clear the Contributing section is for the docsLuca Bruno1-1/+1
2015-06-26all-packages.nix: Add pkgs.overridePackagesLuca Bruno1-0/+1
2015-06-05doc: add user's guide for the Haskell infrastructurePeter Simons1-0/+1
Resolves https://github.com/NixOS/nixpkgs/issues/4941.
2015-01-25Add documentation for nixpkgs.config settings (allowUnfree, ↵Matthias Beyer1-0/+1
allowUnfreePredicate, whitelistedLicenses, blacklistedLicenses)
2014-08-24Nixpkgs manual: Add a Nix expression to buildEelco Dolstra1-3/+2
2014-08-24Nixpkgs manual: Drop author bla blaEelco Dolstra1-17/+1
2014-07-27doc: add section how to build the manualDomen Kožar1-0/+1
2013-10-10Unify the Nixpkgs and NixOS version numbersEelco Dolstra1-1/+1