| Commit message (Collapse) | Author | Age |
|---|
| |\
| |
| | |
babelfish: 1.0.0 -> 1.0.1
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
- remove trailing whitespace
- use spaces for indentation
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| | |
| | | |
scponly: init at 4.8
|
| | | |
| | |
| | |
| | | |
Co-authored-by: Sandro <sandro.jaeckel@gmail.com>
|
| | |/
|/| |
|
| |\ \
| | |
| | | |
babelfish: 0.1.3 -> 1.0.0
|
| | | |
| | |
| | |
| | | |
Notably, adds support for stdout redirections and fixes a failing test.
|
| | |/
|/| |
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The comment at the top of git-and-tools/default.nix said:
/* All git-relates tools live here, in a separate attribute set so that users
* can get a fast overview over what's available.
but unfortunately that hasn't actually held up in practice.
Git-related packages have continued to be added to the top level, or
into gitAndTools, or sometimes both, basically at random, so having
gitAndTools is just confusing. In fact, until I looked as part of
working on getting rid of gitAndTools, one program (ydiff) was
packaged twice independently, once in gitAndTools and once at the top
level (I fixed this in 98c34901969).
So I think it's for the best if we move away from gitAndTools, and
just put all the packages it previously contained at the top level.
I've implemented this here by just making gitAndTools an alias for the
top level -- this saves having loads of lines in aliases.nix. This
means that people can keep referring to gitAndTools in their
configuration, but it won't be allowed to be used within Nixpkgs, and
it won't be presented to new users by e.g. nix search.
The only other change here that I'm aware of is that
appendToName "minimal" is not longer called on the default git
package, because doing that would have necessitated having a private
gitBase variable like before. I think it makes more sense not to do
that anyway, and reserve the "minimal" suffix only for gitMinimal.
|
| | |
|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Part of: https://github.com/NixOS/nixpkgs/issues/108938
meta = with stdenv.lib;
is a widely used pattern. We want to slowly remove
the `stdenv.lib` indirection and encourage people
to use `lib` directly. Thus let’s start with the meta
field.
This used a rewriting script to mostly automatically
replace all occurances of this pattern, and add the
`lib` argument to the package header if it doesn’t
exist yet.
The script in its current form is available at
https://cs.tvl.fyi/depot@2f807d7f141068d2d60676a89213eaa5353ca6e0/-/blob/users/Profpatsch/nixpkgs-rewriter/default.nix
|
| |\ \
| |/
|/| |
wrapFish: add fish shell wrapper package
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This adds a wrapper for fish which allows creating shells pre-initialised
with some completions, functions, and configuration scripts from given paths
or from fish plugin packages (`pkgs.fishPlugins.*`).
This is especially handy when one wants to try a plugin in an ephemeral shell.
GitHub: see https://github.com/NixOS/nixpkgs/pull/107834#discussion_r550612519
|
| |\ \ |
|
| | |\ \
| | | |
| | | | |
oksh: init at 6.8.1
|
| | | | | |
|
| |\| | | |
|
| | | | | |
|
| |\| | |
| | | |
| | | |
| | | | |
https://github.com/NixOS/nixpkgs/commit/b04fc593e7b55fe1f74421b11589f12a339c92e2 seems to have accidentally changed mkDerivation function for dfilemanager and solarus-quest-editor so I have reverted that here.
|
| | | |/
| |/| |
|
| | |\ \
| | | |
| | | | |
fishPlugins: create scope and add some plugins
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
And relocate the installed fish functions to the `vendor_functions.d` so
that they're automatically loaded.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | |/ / |
|
| |\| | |
|
| | |\ \
| | | |
| | | | |
zsh: Disable compiling in /usr/local/... as the site-function directory
|
| | | |/
| | |
| | |
| | |
| | |
| | |
| | | |
With the default configure flags, zsh compiles in a reference to the
"site function" directory that's outside the store path. Under the
right (wrong) circumstances, other builds using zsh can be affected by
these functions.
|
| | | | |
|
| |\| | |
|
| | | | |
|
| | | | |
|
| |\| | |
|
| | | | |
|
| |\| | |
|
| | |\ \
| | | |
| | | | |
any-nix-shell: 1.1.0 -> 1.2.0
|
| | | | | |
|
| | |/ / |
|