| Age | Commit message (Collapse) | Author |
|---|
|
licenses: Make single-version-only GPL explicit
|
|
citrix_workspace: add more features, refactor derivation
|
|
raboof/document-running-perl-scripts-from-the-shell
doc: add section on running ad-hoc Perl programs to the nixpkgs manual
|
|
Co-authored-by: Timo Kaufmann <timokau@zoho.com>
|
|
|
|
|
|
In #89806 it has been reported that the final package is missing a lot
of features like support for the self-service GUI and the
config-management.
While working on supporting those components in the Nix-package, I
decided to refactor the package to simplify the entire setup.
This patch changes the following things:
* Binaries and libraries are patched using the `autoPatchelfHook` to
avoid having unneeded libraries linked (e.g. some programs use gtk2,
others use gtk3).
* Moved source-declarations into their own file.
* Wrapped `configmgr` and `selfservice` and added those to `$out/bin`.
* Don't mention the old `citrix_receiver`-packages in the manual anymore
since those packages were removed in 19.09 and are EOLed anyways.
Closes #89806
|
|
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
|
|
|
|
|
|
|
|
|
|
agda: fix manual build -- blocks nixpkgs-unstable
|
|
/build/doc/manual-full.xml:12764:35: error: ID "build-phase" has already been defined
/build/doc/manual-full.xml:9029:33: error: first occurrence of ID "build-phase"
|
|
https://hydra.nixos.org/build/128037886/nixlog/1/tail
error: element "variable" not allowed anywhere
|
|
maintainers/scripts/update.nix: Add support for auto-commiting changes
|
|
The environment variable will contain the attribute path the script is supposed to update.
|
|
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.
|
|
|
|
We can determine all of them when attrPath is present so we might jsut as well do it.
|
|
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.
|
|
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.
|
|
agda: install literate files
|
|
The documentation incorrectly stated that `installFlags` are passed to
`pip install`.
|
|
|
|
nixos/manual: s/environent/environment/g in configuration.xml
|
|
doc: update lua documentation
|
|
|
|
|
|
|
|
|
|
|
|
Reflects the recent changes to the lua infrastructure.
Packaging from luarocks should be encouraged.
|
|
|
|
|
|
...for rust-packages (into staging)
|
|
Note this also means python3Minimal is now also Python 3.8.
This reverts commit eb1369670b5a4e616ff0cf4100616479b1fa3064 and adds more.
|
|
validatePkgConfig: init
|
|
|
|
* Add id
* Mention rpath
* The control variables do not really have to be env vars (though without structuredAttrs there is not a difference)
|
|
Co-authored-by: cole-h <cole.e.helbling@outlook.com>
Co-authored-by: asymmetric <lorenzo@mailbox.org>
|
|
This adds the `validatePkgConfig` hook, which can be used to validate
pkg-config files in the output(s). Currently, this will just run
`pkg-config --validate` on all `.pc` files, capturing errors such as
the issue that was fixed in #87789.
The hook could be extended in the future with more fine-grained
checks.
|
|
currently LTS 12.x and Current 14.x
|
|
Signed-off-by: Christian Albrecht <christian.albrecht@mayflower.de>
|
|
See also https://discourse.nixos.org/t/rust-build-speed-improvements/7225
|
|
Agda expects a "depend" (not "depends") field in the library description.
|
|
* python3Packages.venvShellHook: add postVenvCreation
* python: docs: add postVenvCreation explaination
|
|
Based on some feedback in #87094 and discussion with @fridh, this re-organizes
the onboarding tutorial in the Nixpkgs manual's python section, so that we start
with the simplest, most ad-hoc examples and work our way up. This progresses
from:
1. How to create an temporary python env at the cmdline, then
2. How to create a specific python env for a single script, then
3. How to create a specific python env for a project in a shell.nix, then
4. How to install a specific python env globally on the system or in a user profile.
Additionally, I've tried to standardize on some of the "best practice" ways of
doing things:
1. Instead of saying that this command style is "supported but strongly not
discouraged", I've just deleted it to avoid confusion.
Bad: nix-shell -p python38Packages.numpy python38Packages.toolz
Good: nix-shell -p 'python38.withPackages(ps: with ps; [ numpy toolz ])'
2. In the portion where we show how to add stuff to the user's
`XDG_CONFIG_HOME`, use overlays instead of `config.nix`. The former can do
everything the latter can do, but is also much more generic and powerful,
because it can compose with other files, compose with other envs, compose
with overlays that do things like swap whether tensorflow and pytorch are
built openblas/mkl/cuda stacks, and so on. The user is eventually going to
see the overlay, so to avoid confusion let's standardize on it.
|
|
Agda rework
|
|
|
