This doesn't change any defaults; I suspect that dropping gtk2 support
would annoy some people so I didn't want to do that without asking
around first.
Putting information in external JSON files is IMHO not an improvement
over the idiomatic style of Nix expressions. The use of JSON doesn't
add anything over Nix expressions (in fact it removes expressive
power). And scattering package info over lots of little files makes
packages less readable over having the info in one file.
termite broke when upgrading Gnome, as this removed a dependency from
the tree. I packaged this dependency (vte-ng) based upon the work of
@globin in https://github.com/NixOS/nixpkgs/issues/22026.
https://nixos.org/nixpkgs/manual/#r-packages contains a method for
setting up an R environment with a specific set of libraries, and it
creates an R wrapper which points R to those libraries.
The package RStudio relies on the standard R package, which then
cannot access any of the libraries specified in a custom R
environment. While one may easily use pkgs.rstudio.override to change
rstudio's R dependency to the custom R environment, this accomplishes
nothing because while RStudio runs the correct R wrapper it clears out
the environment variable R_LIBS_SITE - and so it is still unable to
use any of those packages.
In order to work around this problem, these changes allow the user to
optionally modify rstudio's wrapper to set environment variable
R_PROFILE_USER to an R script which sets R's .libPaths(..) to point to
the same libraries; that script is generated from R_LIBS_SITE in the R
wrapper.
By default, this change has no effect. If R is overridden to
something else, and if useRPackages is changed from its default of
false, then the change described above is made; for instance:
{
packageOverrides = pkgs: let self = pkgs.pkgs; in
rec {
rEnv = pkgs.rWrapper.override {
packages = with self.rPackages; [
dplyr ggplot2 e1071 rpart reshape
];
};
rstudioEnv = pkgs.rstudio.override { R = rEnv; useRPackages = true; };
};
}
This is a bit more involved, because first of all, the tests aren't
distributed in the release tarball and second the test suite currently
doesn't work but there are fixes for it that get released in the next
upstream patch, so we cherry-pick the relevant commits as patches.
We now also switch to fetching the tarball directly from their GitLab
instance, because - as mentioned - it contains the tests and also
contains the icon.index file, which we already had included as a patch
and we can now drop it.
The URLs to the cherry-picked upstream commits are the following:
1f0d7387fd491d32a2ec46a19733d2
All of these commits are in the gajim_0.16 branch and are thus very
likely becoming part of Gajim 0.16.7.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @7c6f434c
