- Removed cargo.lock.patch. Cargo.lock is now available upstream.
- Removed gdk-pixbuf, glib & gsettings-desktop-schemas from
buildInputs. They are propagated by gtk3.
- Added gstreamer plugins to support audio & video.
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.
In hopes of working around
https://github.com/NixOS/nixpkgs/issues/60845. This fetches a gz archive
instead of xz and also fetches the archive from a different source,
hopefully avoiding the issue (whatever ist is caused by).
In addition to that, I think that building directly from VCS is
generally cleaner and more flexible for the following reasons:
- It cuts out and unnecessary middle step.
- It makes sure the version users install is equal to the version users
may have vetted.
- It makes it easy to develop patches or bisect changes by simply
checking out a different rev.
- It avoids using upstream-provided "binary" artifacts like those
generated by autotools.
There ver very many conflicts, basically all due to
name -> pname+version. Fortunately, almost everything was auto-resolved
by kdiff3, and for now I just fixed up a couple evaluation problems,
as verified by the tarball job. There might be some fallback to these
conflicts, but I believe it should be minimal.
Hydra nixpkgs: ?compare=1538299
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.
