| Commit message (Collapse) | Author | Age |
|---|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Refs:
e6754980264fe927320d5ff2dbd24ca4fac9a160
1e9cc5b9844ef603fe160e9f671178f96200774f
793a2fe1e8bb886ca2096c5904e1193dc3268b6d
c19cf65261639f749012454932a532aa7c681e4b
f6544d618f30fae0bc4798c4387a8c7c9c047a7c
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There is a bug in this feature: It allows extra arguments to leak in
from the environment. For example:
$ export extraFlagsArray=date
$ man ls
Note that you get the man page for date rather than for ls. This happens
because 'man' happens to use a wrapper (to add groff to its PATH).
An attempt to fix this was made in 5ae18574fce in PR #19328 for
issue #2537, but 1. That change didn't actually fix the problem because
it addressed makeWrapper's environment during the build process, not the
constructed wrapper script's environment after installation, and 2. That
change was apparently accidentally lost when merged with 7ff6eec5fd8.
Rather than trying to fix the bug again, we remove the extraFlagsArray
feature, since it has never been used in the public repo in the ten
years it has been available.
wrapAclocal continues to use its own, separate flavor of extraFlagsArray
in a more limited context. The analogous bug there was fixed in
4d7d10da6b1 in 2011.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Whenever we create scripts that are installed to $out, we must use runtimeShell
in order to get the shell that can be executed on the machine we create the
package for. This is relevant for cross-compiling. The only use case for
stdenv.shell are scripts that are executed as part of the build system.
Usages in checkPhase are borderline however to decrease the likelyhood
of people copying the wrong examples, I decided to use runtimeShell as well.
|
| | |
|
| |
|
|
|
| |
Support is perhaps claimed upstream, but it's never built successfully
on Hydra, so let's disable that until someone fixes it.
|
| | |
|
| |
|
|
| |
Only acts on one-line dependency lists.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Close #7019.
- update all, and add more paksets
- add config.simutrans.paksets, multiple are possible now
- fix #6719: missing sounds
- move user settings from ~/simutrans to ~/.simutrans
- darwin support is untested (but claimed upstream)
Tested-by: Matthias Beyer <mail@beyermatthias.de>
(and by the author vcunat)
|
| |
|
|
|
|
| |
Should eval cleanly, as far as -A tarball tells me.
Relevant: issue #2999, issue #739
|
| |
|
|
|
| |
Removing more references to the non-existent license "stdenv.lib.licenses.perl5".
Thanks to @FlashKorten for catching those.
|
| | |
|
| |
|
|
| |
This fixes commit b5d19fad6710e786a80f9584e65f4f17e9678c24
|
| | |
|
| | |
|
| |
|
|
|
| |
Today the monitor resolutions are quite high, so I set pak128 as the default.
It's easy to change.
|
| |
|
|
|
|
| |
function, so obsolete it.
svn path=/nixpkgs/branches/stdenv-updates/; revision=31644
|
|
|
svn path=/nixpkgs/trunk/; revision=26523
|