| Commit message (Expand) | Author | Age | Files | Lines |
|---|
| * | Merge pull request #136345 from Pamplemousse/doc•••doc: clarification of dependencies related attributes | Jan Tojnar | 2021-10-26 | 2 | -12/+25 |
| |\ |
|
| | * | doc: clarification of dependencies related attributes•••Signed-off-by: Pamplemousse <xav.maso@gmail.com>
| Pamplemousse | 2021-08-31 | 2 | -12/+25 |
| * | | doc: reference sourceRoot in description of srcs | laikq | 2021-10-05 | 1 | -2/+2 |
| * | | patchelf: fix homepage | ppom | 2021-09-21 | 1 | -1/+1 |
| |/ |
|
| * | doc: stdenv: document meta.mainProgram | figsoda | 2021-08-19 | 1 | -0/+4 |
| * | nixpkgs-docs: when to prefer passthru.tests over installCheckPhase•••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
| Arnout Engelen | 2021-08-14 | 2 | -1/+26 |
| * | manual: Hardening: Remove now-nonexistent ArchWiki link.•••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.
| Niklas Hambüchen | 2021-07-05 | 1 | -1/+1 |
| * | manual: hardening: Fix disabled flags prose being in previous section•••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.
| Niklas Hambüchen | 2021-07-05 | 1 | -9/+18 |
| * | stdenv: introduce dontAddStaticConfigureFlags•••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.
| Alyssa Ross | 2021-06-11 | 1 | -1/+7 |
| * | doc: Use markdown syntax for xrefs•••Syntax is taken from MyST:
https://myst-parser.readthedocs.io/en/latest/using/syntax.html#targets-and-cross-referencing
| Jan Tojnar | 2021-06-07 | 3 | -12/+12 |
| * | doc: prepare for commonmark•••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.
| Jan Tojnar | 2021-06-07 | 4 | -95/+100 |
| * | Fix "platfrom" typos | Emery Hemingway | 2021-04-10 | 1 | -1/+1 |
| * | doc/stdenv/cross: fix typo | sternenseemann | 2021-04-02 | 1 | -1/+1 |
| * | doc: Port stdenv to Markdown•••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
| Jan Tojnar | 2021-03-14 | 2 | -2419/+1215 |
| * | doc: Port stdenv/multiple-output to Markdown | Jan Tojnar | 2021-03-14 | 2 | -261/+128 |
| * | doc: Port stdenv/meta to Markdown | Jan Tojnar | 2021-03-14 | 2 | -349/+194 |
| * | doc: Format | Robert Hensing | 2021-03-04 | 2 | -9/+4 |
| * | Merge pull request #113062 from SuperSandro2000/outputs-update•••doc: update multiple output section with more example paths | Sandro | 2021-03-03 | 1 | -6/+6 |
| |\ |
|
| | * | doc: update multiple output section with more example paths | Sandro Jäckel | 2021-02-14 | 1 | -6/+6 |
| * | | stdenv/cross-compilation: add section on avoiding cross-compiling GCC | Ben Siraphob | 2021-02-22 | 1 | -0/+7 |
| * | | docs/stdenv/cross-compilation: add binutils command section to cookbook | Ben Siraphob | 2021-02-21 | 1 | -4/+8 |
| * | | doc/stdenv/platform-notes: convert to markdown | Ben Siraphob | 2021-02-21 | 2 | -83/+62 |
| |/ |
|
| * | doc: Add anchors to meta attributes | Jan Tojnar | 2021-02-07 | 1 | -15/+15 |
| * | doc: stdenv.lib -> lib•••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.
| Profpatsch | 2021-01-11 | 2 | -12/+12 |
| * | doc/stdenv/cross-compilation.chapter.md typo•••Co-authored-by: John Ericson <git@JohnEricson.me> | Robert Hensing | 2020-12-15 | 1 | -1/+1 |
| * | doc/cross-compilation: Remove confusing re-explanation•••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. | Robert Hensing | 2020-12-15 | 1 | -1/+1 |
| * | doc/stdenv/cross-compilation: convert to markdown | Ben Siraphob | 2020-12-13 | 2 | -394/+197 |
| * | doc/stdenv: Fix xref to gdk-pixbuf setup hook•••DocBook does not support creating labels for unordered list items so we need to add a link label ourselves.
| Jan Tojnar | 2020-12-07 | 1 | -1/+1 |
| * | doc/gnome: Document gdk-pixbuf setup hook•••It was briefly mentioned in stdenv docs but since it interacts with wrapGAppsHook, it should be documented here.
| Jan Tojnar | 2020-11-26 | 1 | -1/+1 |
| * | Make maintainer documentation more direct (#103455)•••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 | Kevin Cox | 2020-11-11 | 1 | -2/+1 |
| * | Merge pull request #96666 from raboof/nixpkgs-document-new-maintainer-convention•••Document conventions around adding new maintainers | Kevin Cox | 2020-11-11 | 1 | -1/+1 |
| |\ |
|
| | * | Document conventions around adding new maintainers•••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>
| Arnout Engelen | 2020-11-11 | 1 | -1/+1 |
| * | | Recover the complicated situation after my bad merge•••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
| Vladimír Čunát | 2020-10-26 | 1 | -1/+6 |
| * | | Revert "Merge #101508: libraw: 0.20.0 -> 0.20.2"•••I'm sorry; I didn't notice it contained staging commits.
This reverts commit 17f5305b6c20df795c365368d2d868266519599e, reversing
changes made to a8a018ddc0a8b5c3d4fa94c94b672c37356bc075.
| Vladimír Čunát | 2020-10-25 | 1 | -6/+1 |
| * | | installShellFiles: Enhance installShellCompletion•••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
| Lily Ballard | 2020-10-08 | 1 | -1/+6 |
| * | | Merge staging-next into staging | Frederik Rietdijk | 2020-10-06 | 1 | -3/+6 |
| |\ \ |
|
| | * | | doc/stdenv: fix build•••https://hydra.nixos.org/build/128037886/nixlog/1/tail
error: element "variable" not allowed anywhere
| zowoq | 2020-10-03 | 1 | -1/+1 |
| | * | | Merge pull request #98304 from jtojnar/updateScript-commit3•••maintainers/scripts/update.nix: Add support for auto-commiting changes | Jan Tojnar | 2020-10-02 | 1 | -3/+6 |
| | |\ \ |
|
| | | * | | maintainers/scripts/update.nix: run update script with UPDATE_NIX_ATTR_PATH•••The environment variable will contain the attribute path the script is supposed to update.
| Jan Tojnar | 2020-09-20 | 1 | -0/+1 |
| | | * | | doc: Undocument attr-set of passthru.updateScript•••We no longer need it for most use cases so I am making it experimental.
I have something in mind where it might be useful in the future (customizing commit messages)
but for now, it would only confuse people.
| Jan Tojnar | 2020-09-20 | 1 | -43/+0 |
| | | * | | maintainers/scripts/update.nix: auto-detect attrPath | Jan Tojnar | 2020-09-20 | 1 | -1/+1 |
| | | * | | maintainers/scripts/update.nix: support filling in auto-commit attributes•••We can determine all of them when attrPath is present so we might jsut as well do it.
| Jan Tojnar | 2020-09-20 | 1 | -0/+3 |
| | | * | | maintainers/scripts/update.nix: support auto-committing by passing attrPath•••Instead of having the updateScript support returning JSON object,
it should be sufficient to specify attrPath in passthru.updateScript.
It is much easier to use.
The former is now considered experimental.
| Jan Tojnar | 2020-09-20 | 1 | -3/+7 |
| | | * | | maintainers/scripts/update.nix: Add support for auto-commiting changes•••Update scripts can now declare features using
passthru.updateScript = {
command = [ ../../update.sh pname ];
supportedFeatures = [ "commit" ];
};
A `commit` feature means that when the update script finishes successfully,
it will print a JSON list like the following:
[
{
"attrPath": "volume_key",
"oldVersion": "0.3.11",
"newVersion": "0.3.12",
"files": [
"/path/to/nixpkgs/pkgs/development/libraries/volume-key/default.nix"
]
}
]
and data from that will be used when update.nix is run with --argstr commit true
to create commits.
We will create a new git worktree for each thread in the pool and run the update
script there. Then we will commit the change and cherry pick it in the main repo,
releasing the worktree for a next change.
| Jan Tojnar | 2020-09-20 | 1 | -3/+41 |
| * | | | | Merge branch 'staging-next' into staging | Jan Tojnar | 2020-09-29 | 1 | -4/+0 |
| |\| | | |
|
| | * | | | Merge pull request #93332 from wamserma/docs-remove-replace-link•••docs.stdenv: remove reference to replace tool | Doron Behar | 2020-09-26 | 1 | -4/+0 |
| | |\ \ \ |
|
| | | * | | | docs.stdenv: remove reference to replace tool | Markus S. Wamser | 2020-07-17 | 1 | -4/+0 |
| * | | | | | Merge branch 'staging-next' into staging | Jan Tojnar | 2020-09-24 | 1 | -1/+1 |
| |\| | | | |
|
| | * | | | | doc: Improve code listings•••By adding prompts and removing unnecessary indentation.
| Jan Tojnar | 2020-09-23 | 1 | -1/+1 |
| | | |/ /
| |/| | |
|
| * / | | | hooks: add moveSystemdUserUnitsHook•••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`.
| Robert Helgesson | 2020-09-12 | 1 | -0/+13 |
| |/ / / |
|
