summary refs log tree commit diff
path: root/doc/default.nix
Commit message (Collapse)AuthorAge
* Generate links to function definitionsGraham Christensen2018-10-05
| | | | | | | | | | Hydra passes the full revision in to the input, which we pass through. If we don't get this ,we try to get it from other sources, or default to master which should have the definition in a close-ish location. All published docs should have theURL resolve properly, only local hackers will have the link break.
* Merge pull request #43857 from volth/unusedFrederik Rietdijk2018-07-20
|\ | | | | [bot] treewide: remove unreferenced code
| * [bot]: remove unreferenced codevolth2018-07-20
| |
* | treewide: remove aliases in nixpkgsMatthew Bauer2018-07-18
|/ | | | | | | | | | | | | | | | | | This makes the command ‘nix-env -qa -f. --arg config '{skipAliases = true;}'’ work in Nixpkgs. Misc... - qtikz: use libsForQt5.callPackage This ensures we get the right poppler. - rewrites: docbook5_xsl -> docbook_xsl_ns docbook_xml_xslt -> docbook_xsl diffpdf: fixup
* manual: make epub a build product on hydra (#41475)Daiderd Jordan2018-06-06
|
* nixpkgs doc: add format Make targetGraham Christensen2018-04-30
|
* treewide: rename version attributesMaximilian Bosch2018-04-28
| | | | | | | | | | | | | | | As suggested in https://github.com/NixOS/nixpkgs/pull/39416#discussion_r183845745 the versioning attributes in `lib` should be consistent to `nixos/version` which implicates the following changes: * `lib.trivial.version` -> `lib.trivial.release` * `lib.trivial.suffix` -> `lib.trivial.versionSuffix` * `lib.nixpkgsVersion` -> `lib.version` As `lib.nixpkgsVersion` is referenced several times in `NixOS/nixpkgs`, `NixOS/nix` and probably several user's setups. As the rename will cause a notable impact it's better to keep `lib.nixpkgsVersion` as alias with a warning yielded by `builtins.trace`.
* nixpkgs docs: syntax highlightGraham Christensen2018-03-26
|
* Move the overridden CSS to overrides.css which can be applied on nixos.orgGraham Christensen2018-03-26
|
* nixpkgs docs: Use SVGs for calloutsGraham Christensen2018-03-26
|
* Validate when building outputsGraham Christensen2018-03-25
|
* docs: Build with a makefileGraham Christensen2018-03-25
|
* Move all nixpkgs doc files in to the doc directoryGraham Christensen2018-03-25
| | | | This makes a makefile-driven developer workflow nicer.
* Emscripten 1.37.16 to 1.37.36 (#37291)Joachim Schiele2018-03-18
| | | | | | | | | | | | | | | | | | | | | | | | | | * trying to build emscriptenPackages not all fail * reading the console.log it turns out python executable is not in place and that is why emconfigure didnt work * backup commit * much more targets are compiling now * added common revisioning * revision bump to 1.37.36 (not tested) * fixed xmllint * forcing unit testing, will implement the tests after i get home * json_c test working * added tests * tiny fixes * added documentation
* mkShell: add builder (#30975)zimbatm2017-12-20
|
* nixpkgs/manual: fix build with new pandocLeonid Onokhov2017-12-20
|
* Update BEAM docsEric Bailey2017-06-22
| | | | | | | | | | | | | | | | | | Improve beam docs: * correct spelling * update per pandoc changes * capitalize titles * capitalize BEAM throughout and use "the BEAM" when referring to the virtual machine. * tweak grammar and phrasing * reformat build-tools-rebar3 section * add more links * re-wrap <para>s Also update <programlisting>s * normalize whitespace * don't double quote homepage * use $ in all shell snippets
* doc: Add rust documentation (#23510)Matthias Beyer2017-03-20
|
* Merge #16501: add a guide about vim pluginsVladimír Čunát2017-01-30
|\
| * Add nixpkgs documentation about how to create a derivation with Vim + pluginsMarc Weber2016-06-25
| |
* | Nixpkgs manual: Fix epub generationEelco Dolstra2016-10-03
| | | | | | | | See 0804f67024f21a75a710e41423561cc0d3472e2f.
* | manual: add node to languages & frameworksLangston Barrett2016-09-20
| | | | | | | | fixes #18609
* | add epub for nixpkgs manual ( #15575 ) (#17053)Christine Koppelt2016-07-20
| | | | | | | | | | | | * add epub for nixpkgs manual ( #15575 ) * change epub filename (interpreted as title & author by some epub readers)
* | Replace `./../*` with `../*` in Nix expressions (#16414)John Ericson2016-06-22
|/
* nixpkgs manual: fix #15735: correct dash renderingVladimír Čunát2016-05-27
|
* nixpkgs manual: cleanup (#15611)Eric Sagnes2016-05-22
|
* manual: use a better relaxng validation tool #4966Domen Kožar2016-03-30
|
* Documentation: fix usage of useChaptersFrederik Rietdijk2016-03-12
|
* Documentation: rewrite PythonFrederik Rietdijk2016-03-12
| | | | | | - Rewrite current documentation - Add introduction/tutorial - Convert to markdown
* Revert "Documentation: rewrite Python docs"Frederik Rietdijk2016-03-05
|
* Documentation: rewrite PythonFrederik Rietdijk2016-03-05
| | | | | | - Rewrite current documentation - Add introduction/tutorial - Convert to markdown
* nixpkgs manual: add basic R documentation, fixes #13362Michel Kuhlmann2016-02-22
| | | | also fixes #13243
* DOC: Overview of Nixpkgs/channels/Hydra/tests (close #11263)Frederik Rietdijk2016-02-21
| | | | | | | | | | | | | | What I missed when I began using Nix and NixOS was a clear overview of how packages, channels, Hydra, the master branch and updates to channels relate to each other. I've noticed I am not the only one, given the amount of times these questions pop up. For now I propose to include this in the Nixpkgs manual, since this seems to be the best fit. However, I think it would be good to include this in either a new manual, i.e., a user manual, or an 'official' tutorial.
* nixpkgs manual: add idris docs generated from *.mdVladimír Čunát2015-12-21
| | | | | | I also modified the nesting approach in haskell docs to allow more uniform handling of markdown -> docbook conversions. /cc #11308.
* 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.
* doc: generate haskell-users-guide.xml from Markdown input via PandocPeter Simons2015-09-30
| | | | | | Editing Docbook is no fun, IMHO, so I'd rather store the Haskell documentation in Markdown format and use Pandoc to convert that into Docbook as part of the build process.
* doc/default.nix: fix Emacs syntax highlighting (no functional change)Peter Simons2015-09-30
|
* nixpkgs-manual: fix calloutsLuca Bruno2015-06-30
|
* Nixpkgs manual: Add a Nix expression to buildEelco Dolstra2014-08-24
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-06-01 21:08:46 +0000