| Commit message (Collapse) | Author | Age |
|\ |
|
| | |
|
| |
| |
| | |
Co-Authored-By: guibou <guillaum.bouchard@gmail.com>
|
| | |
|
|\| |
|
| |
| |
| |
| | |
nix-repl has been deprecated
|
|/
|
|
| |
ghc needs it to fail to correctly detect it for later.
|
|\
| |
| | |
Favor HTTPS URLs - the GNU edition
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
HTTP -> HTTPS for :
- http://gnu.org/
- http://www.gnu.org/
- http://elpa.gnu.org/
- http://lists.gnu.org/
- http://gcc.gnu.org/
- http://ftp.gnu.org/ (except in fetchurl mirrors)
- http://bugs.gnu.org/
|
|\ \
| |/
|/| |
update.nix: Run update scripts in parallel
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
To make updating large attribute sets faster, the update scripts
are now run in parallel.
Please note the following changes in semantics:
- The string passed to updateScript needs to be a path to an executable file.
- The updateScript can also be a list: the tail elements will then be passed
to the head as command line arguments.
|
| |
| |
| | |
For whatever reason, nix-build ... --argstr a.b "c" doesn't work. It fails quitely so it's best to use an example here that works.
|
|\ \
| | |
| | |
| | |
| | | |
* pr-51111:
doc: document upgrading Ruby packages
|
| | |
| | |
| | |
| | |
| | |
| | | |
As requested[1] by @Ekleog.
[1]: https://github.com/NixOS/nixpkgs/pull/51040#issuecomment-441642763
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Encouraging to put container elements on their own lines to minimize
diffs, merge conflicts and making re-ordering easier.
Nix doesn't suffer the restrictions of other languages where commas are
used to separate list items.
|
|\ \ \
| | | |
| | | | |
autoPatchelfHook: Fixes/improvements for Android SDK emulator
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
First of all, this makes the existing documentation a bit more clear on
what autoPatchelfHook is all about, because after discussing with
@svanderburg - who wrote a similar implementation - the rationale about
autoPatchelfHook wasn't very clear in the documentation.
I also added the recent changes around being able to use autoPatchelf
manually and the new --no-recurse flag.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |/ /
|/| | |
|
|\ \ \
| | |/
| |/| |
|
| | |
| | |
| | |
| | | |
Regression from #50674. Section IDs cannot contain spaces.
|
| | |
| | |
| | |
| | | |
The link doesn’t work and it’s not very important to the documentation anyway.
|
| | |
| | |
| | |
| | |
| | | |
This makes things more consistent. It’s also how GitHub refers to pull
requests.
|
| | |
| | |
| | |
| | | |
More cleanups and stuff. May need to be split up.
|
| | |
| | |
| | |
| | | |
xcbuild doesn’t work exactly like xcode in some ways.
|
| | |
| | |
| | |
| | | |
Lots of reworking here. May need to be split up.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Here I document setup hooks provided by:
- cmake
- xcbuildHook
- meson
- ninja
- unzip
- wafHook
- scons
|
| | |
| | |
| | |
| | | |
This seems like a useful thing to document
|
| | |
| | |
| | |
| | | |
This makes more sense in context.
|
| |/ |
|
| | |
|
|\| |
|
| |\ |
|
| | | |
|
|\| | |
|
| | | |
|
| | | |
|
| |\ \
| | | |
| | | | |
nixpkgs idris docs: Update and improve
|
| | |/ |
|
|\| | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Nix currently rejects derivations in `meta` values. This works around
that limitation by using `passthru` instead.
Closes https://github.com/NixOS/nixpkgs/issues/50230
|
| | |
| | |
| | |
| | | |
Its job is already handled by `requiredSystemFeatures`
|
|\| | |
|
| |/
| |
| |
| | |
The default for `python3` is currently `python36`.
|
|\| |
|
| |\
| | |
| | | |
buildDunePackage: add support function and use it in a few packages
|
| | | |
|
| |/
| |
| |
| |
| |
| | |
It's incorrect (preferLocalBuild does not prevent uploading to binary
caches) and is not a stdenv attribute (it's already documented in the
Nix manual).
|
| |\
| | |
| | | |
[RFC] Use `meta.tests` to link from packages to the tests that test them
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Rationale
---------
Currently, tests are hard to discover. For instance, someone updating
`dovecot` might not notice that the interaction of `dovecot` with
`opensmtpd` is handled in the `opensmtpd.nix` test.
And even for someone updating `opensmtpd`, it requires manual work to go
check in `nixos/tests` whether there is actually a test, especially
given not so many packages in `nixpkgs` have tests and this is thus most
of the time useless.
Finally, for the reviewer, it is much easier to check that the “Tested
via one or more NixOS test(s)” has been checked if the file modified
already includes the list of relevant tests.
Implementation
--------------
Currently, this commit only adds the metadata in the package. Each
element of the `meta.tests` attribute is a derivation that, when it
builds successfully, means the test has passed (ie. following the same
convention as NixOS tests).
Future Work
-----------
In the future, the tools could be made aware of this `meta.tests`
attribute, and for instance a `--with-tests` could be added to
`nix-build` so that it also builds all the tests. Or a `--without-tests`
to build without all the tests. @Profpatsch described in his NixCon talk
such systems.
Another thing that would help in the future would be the possibility to
reasonably easily have cross-derivation nix tests without the whole
NixOS VM stack. @7c6f434c already proposed such a system.
This RFC currently handles none of these concerns. Only the addition of
`meta.tests` as metadata to be used by maintainers to remember to run
relevant tests.
|