summary refs log tree commit diff
path: root/doc/manual.xml
Commit message (Collapse)AuthorAge
* doc/using: convert to markdownfricklerhandwerk2021-04-23
|
* doc/contributing/*.xml: Convert to markdownBobby Rong2021-04-23
|
* Merge pull request #116459 from Pamplemousse/document_vulnerability_roundupChristian Kauhaus2021-03-19
|\ | | | | documentation: Add content about Vulnerability roundups
| * documentation: Add content about Vulnerability roundupsPamplemousse2021-03-17
| | | | | | | | Signed-off-by: Pamplemousse <xav.maso@gmail.com>
* | doc: Port stdenv to MarkdownJan Tojnar2021-03-14
| | | | | | | | | | | | | | | | | | | | | | | | 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
* | doc: Port stdenv/multiple-output to MarkdownJan Tojnar2021-03-14
| |
* | doc: Port stdenv/meta to MarkdownJan Tojnar2021-03-14
|/
* doc/stdenv/platform-notes: convert to markdownBen Siraphob2021-02-21
|
* Convert fetchers from DocBook to CommonMarkAndersonTorres2020-12-17
|
* Convert trivial-builders from DocBook to CommonMarkAndersonTorres2020-12-17
|
* doc/stdenv/cross-compilation: convert to markdownBen Siraphob2020-12-13
|
* doc: Rename submitting-changes to chapterJan Tojnar2020-12-05
|
* doc: rename guide to 'Nixpkgs Manual'Arnout Engelen2020-09-24
| | | | | 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.
* nixpkgs manual: move builders into one folderFrederik Rietdijk2019-10-30
|
* nixpkgs manual: move using chapters into one folderFrederik Rietdijk2019-10-30
|
* nixpkgs manual: move stdenv chapters into one folderFrederik Rietdijk2019-10-30
|
* nixpkgs manual: move contributing chapters into one folderFrederik Rietdijk2019-10-30
|
* nixpkgs manual: various improvements in introductionFrederik Rietdijk2019-10-30
| | | | | | | - rename to preface to be inline with NixOS manual - refer to other manuals - use https - change example channel to 19.09
* doc: move fhs and mkShell under builders/specialFrederik Rietdijk2019-10-21
| | | | | | 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...
* doc: move overrides into separate chapterFrederik Rietdijk2019-10-21
|
* doc: move image builders into new images chapterFrederik Rietdijk2019-10-21
|
* doc: move fetchers and trivial builders under buildersFrederik Rietdijk2019-10-20
|
* doc: split packages part into xml file per packageFrederik Rietdijk2019-10-20
|
* doc: merge package notes and package-specific notesFrederik Rietdijk2019-10-20
| | | | | Maybe there was an idea behind this separation, but looking at the contents I don't see any reason for these being separate.
* doc: organize chapters into parts, and reduce toc depthFrederik Rietdijk2019-10-20
| | | | | | | | | 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.
* [RFC] manual: rename to users and contributors manual, add some user notes ↵Michael Raskin2019-05-22
| | | | | | | … (#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
* nixpkgs docs: format =)Graham Christensen2018-05-01
|
* Move all nixpkgs doc files in to the doc directoryGraham Christensen2018-03-25
| | | | This makes a makefile-driven developer workflow nicer.
* docs: add section on common darwin issuesDaiderd Jordan2017-11-01
|
* nixpkgs docs: Cross compilation docsJohn Ericson2017-01-24
|
* Add overlays mechanism to Nixpkgs.Nicolas B. Pierron2017-01-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* manual: reviewing contributions nixos -> nixpkgs (#20626)Eric Sagnes2016-11-22
|
* nixpkgs manual: cleanup (#15611)Eric Sagnes2016-05-22
|
* beam-support: update registry to latest '59b836d'Eric Merritt2016-04-23
|
* nixpkgs manual: add multiple-output chapterVladimír Čunát2016-04-07
|
* erlang support: Add minimal documentation to nixEric Merritt2016-01-15
| | | | | | 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
* nixpkgs manual: split languages into separate filesVladimír Čunát2015-12-19
| | | | | | | | 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.
* Fixed a syntax error in the buildFHSChrootEnv example. Also, fixed the ↵Avery Glitch2015-12-18
| | | | manual.xml so it actually builds.
* Move the submitting-changes down, after coding conventionsCillian de Róiste2015-07-12
|
* Move the details from CONTRIBUTING.md to the manual #8734Cillian de Róiste2015-07-12
|
* doc: make it clear the Contributing section is for the docsLuca Bruno2015-06-30
|
* all-packages.nix: Add pkgs.overridePackagesLuca Bruno2015-06-26
|
* doc: add user's guide for the Haskell infrastructurePeter Simons2015-06-05
| | | | Resolves https://github.com/NixOS/nixpkgs/issues/4941.
* Add documentation for nixpkgs.config settings (allowUnfree, ↵Matthias Beyer2015-01-25
| | | | allowUnfreePredicate, whitelistedLicenses, blacklistedLicenses)
* Nixpkgs manual: Add a Nix expression to buildEelco Dolstra2014-08-24
|
* Nixpkgs manual: Drop author bla blaEelco Dolstra2014-08-24
|
* doc: add section how to build the manualDomen Kožar2014-07-27
|
* Unify the Nixpkgs and NixOS version numbersEelco Dolstra2013-10-10
|
* * Sync CSS with the Nix manual.Eelco Dolstra2012-05-11
| | | | svn path=/nixpkgs/trunk/; revision=34062
* * Moved the coding conventions from maintainers/docs to the NixpkgsEelco Dolstra2009-09-25
| | | | | | | manual. * Removed some out-dated files from maintainers/docs. svn path=/nixpkgs/trunk/; revision=17419