about summary refs log tree commit diff
path: root/doc/stdenv
AgeCommit message (Collapse)AuthorFilesLines
2021-10-26Merge pull request #136345 from Pamplemousse/docJan Tojnar2-12/+25
doc: clarification of dependencies related attributes
2021-10-05doc: reference sourceRoot in description of srcslaikq1-2/+2
2021-09-21patchelf: fix homepageppom1-1/+1
2021-08-31doc: clarification of dependencies related attributesPamplemousse2-12/+25
Signed-off-by: Pamplemousse <xav.maso@gmail.com>
2021-08-19doc: stdenv: document meta.mainProgramfigsoda1-0/+4
2021-08-14nixpkgs-docs: when to prefer passthru.tests over installCheckPhaseArnout Engelen2-1/+26
And mention you can have either lightweight 'package' or more heavyweight 'NixOS' (module) tests. This was suggested at https://github.com/ryantm/nixpkgs-update/issues/260#issuecomment-821287971 and discussed further at https://github.com/NixOS/nixpkgs/pull/119731
2021-07-05manual: Hardening: Remove now-nonexistent ArchWiki link.Niklas Hambüchen1-1/+1
The page has been replaced by the much more general page https://wiki.archlinux.org/title/Security#Packages which is barely talking about hardening flags any more.
2021-07-05manual: hardening: Fix disabled flags prose being in previous sectionNiklas Hambüchen1-9/+18
This confused the hell out of me, as I didn't spot the > The following flags are disabled by default ... when reading about `pie`, because that sentence was hidden in the previous hardening flag's section. Also explain that `pie` hardening is on by default on musl.
2021-06-11stdenv: introduce dontAddStaticConfigureFlagsAlyssa Ross1-1/+7
With removeUnknownConfigureFlags, it's impossible to express a package that needs --enable-static, but will not accept --disable-shared, without overriding the result of removeUnknownConfigureFlags _again_ in pkgs/top-level/static.nix. It would be much better (and more in line with the rest of Nixpkgs) if we encoded changes needed for static builds in package definitions themselves, rather than in an ever-expanding list in static.nix. This is especially true when doing it in static.nix is going to require multiple overrides to express what could be expressed with stdenv options. So as a step in that direction, and to fix the problem described above, here I replace removeUnknownConfigureFlags with a new stdenv option, dontAddStaticConfigureFlags. With this mechanism, a package that needs one but not both of the flags just needs to set dontAddStaticConfigureFlags and then set up configureFlags manually based on stdenv.hostPlatform.isStatic.
2021-06-07doc: Use markdown syntax for xrefsJan Tojnar3-12/+12
Syntax is taken from MyST: https://myst-parser.readthedocs.io/en/latest/using/syntax.html#targets-and-cross-referencing
2021-06-07doc: prepare for commonmarkJan Tojnar4-95/+100
We are still using Pandoc’s Markdown parser, which differs from CommonMark spec slightly. Notably: - Line breaks in lists behave differently. - Admonitions do not support the simpler syntax https://github.com/jgm/commonmark-hs/issues/75 - The auto_identifiers uses a different algorithm – I made the previous ones explicit. - Languages (classes) of code blocks cannot contain whitespace so we have to use “pycon” alias instead of Python “console” as GitHub’s linguist While at it, I also fixed the following issues: - ShellSesssion was used - Removed some pointless docbook tags.
2021-04-10Fix "platfrom" typosEmery Hemingway1-1/+1
2021-04-02doc/stdenv/cross: fix typosternenseemann1-1/+1
2021-03-14doc: Port stdenv to MarkdownJan Tojnar2-2419/+1215
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 Tojnar2-261/+128
2021-03-14doc: Port stdenv/meta to MarkdownJan Tojnar2-349/+194
2021-03-04doc: FormatRobert Hensing2-9/+4
2021-03-03Merge pull request #113062 from SuperSandro2000/outputs-updateSandro1-6/+6
doc: update multiple output section with more example paths
2021-02-22stdenv/cross-compilation: add section on avoiding cross-compiling GCCBen Siraphob1-0/+7
2021-02-21docs/stdenv/cross-compilation: add binutils command section to cookbookBen Siraphob1-4/+8
2021-02-21doc/stdenv/platform-notes: convert to markdownBen Siraphob2-83/+62
2021-02-14doc: update multiple output section with more example pathsSandro Jäckel1-6/+6
2021-02-07doc: Add anchors to meta attributesJan Tojnar1-15/+15
2021-01-11doc: stdenv.lib -> libProfpatsch2-12/+12
Part of: https://github.com/NixOS/nixpkgs/issues/108938 Changing the documentation to not refer to stdenv.lib is the first step to make people use it directly.
2020-12-15doc/stdenv/cross-compilation.chapter.md typoRobert Hensing1-1/+1
Co-authored-by: John Ericson <git@JohnEricson.me>
2020-12-15doc/cross-compilation: Remove confusing re-explanationRobert Hensing1-1/+1
See https://github.com/NixOS/nixpkgs/issues/106950 > They way it's worded says buildInputs are for build-time and nativeBuildInputs are for run-time. The other documentation leads me to believe it is the other way around.
2020-12-13doc/stdenv/cross-compilation: convert to markdownBen Siraphob2-394/+197
2020-12-07doc/stdenv: Fix xref to gdk-pixbuf setup hookJan Tojnar1-1/+1
DocBook does not support creating labels for unordered list items so we need to add a link label ourselves.
2020-11-26doc/gnome: Document gdk-pixbuf setup hookJan Tojnar1-1/+1
It was briefly mentioned in stdenv docs but since it interacts with wrapGAppsHook, it should be documented here.
2020-11-11Make maintainer documentation more direct (#103455)Kevin Cox1-2/+1
Additionally fixes the "list of names and emails" to be a list of maintainer expressions. A follow-up from the discussion in https://github.com/NixOS/nixpkgs/pull/96666
2020-11-11Merge pull request #96666 from raboof/nixpkgs-document-new-maintainer-conventionKevin Cox1-1/+1
Document conventions around adding new maintainers
2020-11-11Document conventions around adding new maintainersArnout Engelen1-1/+1
Adding them to `maintainers/maintainer-list` in a separate commit. Co-Authored-By: Pavol Rusnak <pavol@rusnak.io> Co-Authored-By: Atemu <atemu.main@gmail.com> Co-Authored-By: Kevin Cox <kevincox@kevincox.ca>
2020-10-26Recover the complicated situation after my bad mergeVladimír Čunát1-1/+6
I made a mistake merge. Reverting it in c778945806b undid the state on master, but now I realize it crippled the git merge mechanism. As the merge contained a mix of commits from `master..staging-next` and other commits from `staging-next..staging`, it got the `staging-next` branch into a state that was difficult to recover. I reconstructed the "desired" state of staging-next tree by: - checking out the last commit of the problematic range: 4effe769e2b - `git rebase -i --preserve-merges a8a018ddc0` - dropping the mistaken merge commit and its revert from that range (while keeping reapplication from 4effe769e2) - merging the last unaffected staging-next commit (803ca85c209) - fortunately no other commits have been pushed to staging-next yet - applying a diff on staging-next to get it into that state
2020-10-25Revert "Merge #101508: libraw: 0.20.0 -> 0.20.2"Vladimír Čunát1-6/+1
I'm sorry; I didn't notice it contained staging commits. This reverts commit 17f5305b6c20df795c365368d2d868266519599e, reversing changes made to a8a018ddc0a8b5c3d4fa94c94b672c37356bc075.
2020-10-08installShellFiles: Enhance installShellCompletionLily Ballard1-1/+6
Teach installShellCompletion how to install completions from a named pipe. Also add a convenience flag `--cmd NAME` that synthesizes the name for each completion instead of requiring repeated `--name` flags. Usage looks something like installShellCompletion --cmd foobar \ --bash <($out/bin/foobar --bash-completion) \ --fish <($out/bin/foobar --fish-completion) \ --zsh <($out/bin/foobar --zsh-completion) Fixes #83284
2020-10-06Merge staging-next into stagingFrederik Rietdijk1-3/+6
2020-09-29Merge branch 'staging-next' into stagingJan Tojnar1-4/+0
2020-09-26Merge pull request #93332 from wamserma/docs-remove-replace-linkDoron Behar1-4/+0
docs.stdenv: remove reference to replace tool
2020-09-24Merge branch 'staging-next' into stagingJan Tojnar1-1/+1
2020-09-23doc: Improve code listingsJan Tojnar1-1/+1
By adding prompts and removing unnecessary indentation.
2020-09-12hooks: add moveSystemdUserUnitsHookRobert Helgesson1-0/+13
This hook moves systemd user service file from `lib/systemd/user` to `share/systemd/user`. This is to allow systemd to find the user services when installed into a user profile. The `lib/systemd/user` path does not work since `lib` is not in `XDG_DATA_DIRS`.
2020-09-05Merge pull request #76794 from ↵Silvan Mosberger1-22/+52
dudebout/document-nix-env-multiple-output-install-bug document nix-env bug relating to multiple output installation
2020-09-05document nix-env bug relating to multiple output installationNicolas Dudebout1-22/+52
2020-08-15doc: Add anchors to stdenv variablesJan Tojnar1-97/+97
Wanted to link them.
2020-07-18Merge pull request #92348 from jtojnar/explicit-only-gplJan Tojnar1-3/+3
licenses: Make single-version-only GPL explicit
2020-07-17docs.stdenv: remove reference to replace toolMarkus S. Wamser1-4/+0
2020-07-05licenses: Make single-version-only GPL explicitJan Tojnar1-3/+3
I commonly see people use the former when they should use the latter. Would be also in line with the SPDX change https://www.gnu.org/licenses/identify-licenses-clearly.html
2020-06-22add autoPatchelfIgnoreMissingDeps to auto-patchelf.shDavHau1-0/+3
2020-10-03doc/stdenv: fix buildzowoq1-1/+1
https://hydra.nixos.org/build/128037886/nixlog/1/tail error: element "variable" not allowed anywhere
2020-10-02Merge pull request #98304 from jtojnar/updateScript-commit3Jan Tojnar1-3/+6
maintainers/scripts/update.nix: Add support for auto-commiting changes
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-08-16 11:08:04 +0000