Commit Graph

29 Commits

Author SHA1 Message Date
Benjamin Hipple
9131efe52d tree-sitter: 0.15.7 -> 0.16.4
Includes some bugfixes/cleanups to the scripts and packaging, a run of the
updater, a bump of the version, an upgrade to the newer cargo fetcher in #79975,
and gets the web assembly portion to compile successfully.

Fixes #75863
2020-02-15 00:33:54 -05:00
Benjamin Hipple
eb11feaa0b treewide: change fetchCargoTarball default to opt-out
Changes the default fetcher in the Rust Platform to be the newer
`fetchCargoTarball`, and changes every application using the current default to
instead opt out.

This commit does not change any hashes or cause any rebuilds. Once integrated,
we will start deleting the opt-outs and recomputing hashes.

See #79975 for details.
2020-02-13 22:41:37 -08:00
Maximilian Bosch
9842c4b107
treewide: update which packages I'm currently maintaining
Idea shamelessly stolen from 4e60b0efae.

I realized that I don't really know anymore where I'm listed as maintainer and what
I'm actually (co)-maintaining which means that I can't proactively take
care of packages I officially maintain.

As I don't have the time, energy and motivation to take care of stuff I
was interested in 1 or 2 years ago (or packaged for someone else in the
past), I decided that I make this explicit by removing myself from several
packages and adding myself in some other stuff I'm now interested in.

I've seen it several times now that people remove themselves from a
package without removing the package if it's unmaintained after that
which is why I figured that it's fine in my case as the affected pkgs
are rather low-prio and were pretty easy to maintain.
2019-12-26 15:27:47 +01:00
Alyssa Ross
7887a81193
treewide: fix cargoSha256 (again)
cargo-vendor output was changed in a4fc84de44.
2019-12-20 20:08:53 +00:00
Robin Gloster
4e60b0efae
treewide: update globin's maintained drvs 2019-08-20 19:36:05 +02:00
Lily Ballard
cd3718281f ripgrep: 11.0.1 -> 11.0.2 2019-08-01 21:37:52 -07:00
Aria Edmonds
94e62564cb ripgrep: turn withPCRE2 on by default
This is set by default in archpkgs and debian repos, and would confuse
fewer new users.
2019-07-22 05:35:42 -04:00
Alyssa Ross
062210bdff treewide: update cargoSha256 hashes for cargo-vendor upgrade
A recent upgrade of cargo-vendor changed its output slightly, which
broke all cargoSha256 hashes in nixpkgs.
See https://github.com/NixOS/nixpkgs/issues/60668 for more information.

Since then, a few hashes have been fixed in master by hand, but there
were a lot still to do, so I did all of the ones left over with some
scripts I wrote.

The one hash I wasn’t able to update was habitat's, because it’s
currently broken and the build doesn’t get far enough to produce a
hash anyway.
2019-06-01 15:17:52 +00:00
Vladyslav M
f469313353
ripgrep: 11.0.0 -> 11.0.1 2019-04-16 23:27:05 +03:00
Lily Ballard
7946a284c2 ripgrep: 0.10.0 -> 11.0.0 2019-04-16 00:00:16 -07:00
Vladyslav M
3b4ab85f01 ripgrep: 0.9.0 -> 0.10.0 (#46331) 2018-09-08 14:21:25 +02:00
Vladyslav M
2ce2f721b8 ripgrep: 0.8.1 -> 0.9.0 (#44473) 2018-08-04 22:59:33 +02:00
volth
52f53c69ce pkgs/*: remove unreferenced function arguments 2018-07-21 02:48:04 +00:00
Vladyslav M
70cc99005e ripgrep: 0.8.0 -> 0.8.1 2018-02-21 20:36:36 +02:00
dywedir
d0501e96ba ripgrep: 0.7.1 -> 0.8.0, install shell completions 2018-02-13 15:58:13 +02:00
dywedir
9af922ac78 ripgrep: 0.6.0 -> 0.7.1 2017-10-23 11:01:52 +03:00
Kevin Cox
5f8cf0048e rust: update cargo builder to fetch registry dynamically
The biggest benefit is that we no longer have to update the registry
package. This means that just about any cargo package can be built by
nix. No longer does `cargo update` need to be feared because it will
update to packages newer then what is available in nixpkgs.

Instead of fetching the cargo registry this bundles all the source code
into a "vendor/" folder.

This also uses the new --frozen and --locked flags which is nice.

Currently cargo-vendor only provides binaries for Linux and
macOS 64-bit. This can be solved by building it for the other
architectures and uploading it somewhere (like the NixOS cache).

This also has the downside that it requires a change to everyone's deps
hash. And if the old one is used because it was cached it will fail to
build as it will attempt to use the old version. For this reason the
attribute has been renamed to `cargoSha256`.

Authors:
* Kevin Cox <kevincox@kevincox.ca>
* Jörg Thalheim <Mic92@users.noreply.github.com>
* zimbatm <zimbatm@zimbatm.com>
2017-10-23 00:30:47 +01:00
dywedir
5db77990db ripgrep: 0.5.2 -> 0.6.0 2017-08-25 01:25:02 +03:00
mimadrid
56393d4471
ripgrep: 0.5.1 -> 0.5.2 2017-05-15 20:21:49 +02:00
Cray Elliott
df86c9731b ripgrep: 0.5.0 -> 0.5.1 2017-04-22 19:03:09 -07:00
Daiderd Jordan
c8ddac7c76 Merge pull request #23864 from mimadrid/update/ripgrep-0.5.0
ripgrep: 0.4.0 -> 0.5.0
2017-03-15 21:42:23 +01:00
mimadrid
363cfbd23d
ripgrep: 0.4.0 -> 0.5.0 2017-03-13 22:48:38 +01:00
c74d
161d73c163 ripgrep: install man-page
Modify the `ripgrep` package to install the tool's manual page.

I have tested this commit per nixpkgs manual section 11.1 ("Making
patches").
2017-03-10 07:12:16 +00:00
mimadrid
51592a3f49
ripgrep: 0.3.2 -> 0.4.0 2017-02-13 22:38:36 +01:00
Ricardo M. Correia
096e8ab45f Merge pull request #21218 from mimadrid/update/ripgrep-0.3.2
ripgrep: 0.2.1 -> 0.3.2
2016-12-17 13:39:56 +01:00
mimadrid
2077a60c2f
ripgrep: 0.2.1 -> 0.3.2 2016-12-17 00:16:40 +01:00
Tom Saeger
e0e1bdc25c Fixup description of ripgrep. 2016-12-15 17:41:22 -06:00
Benno Fünfstück
4c493a32f9 ripgrep: update 0.1.17 -> 0.2.1 2016-09-29 00:51:14 +02:00
Paul Colomiets
1255d60b35 ripgrep: init at 0.1.17 2016-09-23 23:53:54 +03:00