nixpkgs/pkgs/applications/office/spice-up/default.nix

{ lib
, stdenv
, fetchFromGitHub
, nix-update-script
, meson
, ninja
, pkg-config
, python3
, vala
, wrapGAppsHook
, glib
, gtk3
, json-glib
, libevdev
, libgee
, libgudev
, libsoup
, pantheon
}:

stdenv.mkDerivation rec {
  pname = "spice-up";
  version = "1.9.1";

  src = fetchFromGitHub {
    owner = "Philip-Scott";
    repo = "Spice-up";
    rev = version;
    sha256 = "sha256-FI6YMbqZfaU19k8pS2eoNCnX8O8F99SHHOxMwHC5fTc=";
  };

  nativeBuildInputs = [
    meson
    ninja
    pkg-config
    python3
    vala
    wrapGAppsHook
  ];

  buildInputs = [
    glib
    gtk3
    json-glib
    libevdev
    libgee
    libgudev
    libsoup
    pantheon.granite
  ];

  postPatch = ''
    chmod +x meson/post_install.py
    patchShebangs meson/post_install.py
  '';

  passthru = {
    updateScript = nix-update-script {
      attrPath = pname;
    };
  };

  meta = with lib; {
    description = "Create simple and beautiful presentations";
    homepage = "https://github.com/Philip-Scott/Spice-up";
    maintainers = with maintainers; [ samdroid-apps xiorcale ] ++ teams.pantheon.members;
    platforms = platforms.linux;
    # The COPYING file has GPLv3; some files have GPLv2+ and some have GPLv3+
    license = licenses.gpl3Plus;
    mainProgram = "com.github.philip_scott.spice-up";
  };
}
spice-up: 1.8.2 -> 1.9.1 2022-01-14 05:29:26 +01:00			`{ lib`
			`, stdenv`
spice-up: init at 1.2.1 2018-02-09 12:30:09 +01:00			`, fetchFromGitHub`
treewide: use nix-update updateScript for packages I maintain 2020-07-29 18:33:39 +02:00			`, nix-update-script`
spice-up: 1.8.2 -> 1.9.1 2022-01-14 05:29:26 +01:00			`, meson`
spice-up: 1.7.0 -> 1.8.0 2019-03-05 22:57:51 +01:00			`, ninja`
pkgs/applications: pkgconfig -> pkg-config 2021-01-17 03:09:27 +01:00			`, pkg-config`
spice-up: 1.8.2 -> 1.9.1 2022-01-14 05:29:26 +01:00			`, python3`
			`, vala`
			`, wrapGAppsHook`
			`, glib`
			`, gtk3`
tree-wide: autorename gnome packages to use dashes 2018-02-25 03:23:58 +01:00			`, json-glib`
spice-up: init at 1.2.1 2018-02-09 12:30:09 +01:00			`, libevdev`
spice-up: 1.7.0 -> 1.8.0 2019-03-05 22:57:51 +01:00			`, libgee`
spice-up: 1.8.2 -> 1.9.1 2022-01-14 05:29:26 +01:00			`, libgudev`
spice-up: 1.3.2 -> 1.6.0 2018-10-31 23:25:22 +01:00			`, libsoup`
spice-up: 1.8.2 -> 1.9.1 2022-01-14 05:29:26 +01:00			`, pantheon`
pantheon: use latest vala elementary OS's ecosystem is curated around Ubuntu's LTS releases. This means the development platform for their curated applications always includes a LTS version of vala (in 18.04 it's 0.40). Because of how vala development works it suspect some of these applications to have serious issues if complied with the latest vala. However in the past year or so, for Pantheon at least, I don't think their applications will have much issues with latest vala, and if there is I don't think they'd be difficult to fix. In this single regard they've become more responsive since their preferred language is vala. As for the curated applications I have less of this confidence in. So I'd have to be accept less applications, but that's something I'm willing to compromise on. And this is easily reversible or could be done on a per-application basis. And nix already makes this trivial. 2019-10-10 04:47:37 +02:00			`}:`
spice-up: init at 1.2.1 2018-02-09 12:30:09 +01:00
			`stdenv.mkDerivation rec {`
spice-up: 1.7.0 -> 1.8.0 2019-03-05 22:57:51 +01:00			`pname = "spice-up";`
spice-up: 1.8.2 -> 1.9.1 2022-01-14 05:29:26 +01:00			`version = "1.9.1";`
spice-up: init at 1.2.1 2018-02-09 12:30:09 +01:00
			`src = fetchFromGitHub {`
			`owner = "Philip-Scott";`
			`repo = "Spice-up";`
			`rev = version;`
spice-up: 1.8.2 -> 1.9.1 2022-01-14 05:29:26 +01:00			`sha256 = "sha256-FI6YMbqZfaU19k8pS2eoNCnX8O8F99SHHOxMwHC5fTc=";`
spice-up: init at 1.2.1 2018-02-09 12:30:09 +01:00			`};`
spice-up: 1.3.2 -> 1.6.0 2018-10-31 23:25:22 +01:00
spice-up: init at 1.2.1 2018-02-09 12:30:09 +01:00			`nativeBuildInputs = [`
spice-up: 1.8.2 -> 1.9.1 2022-01-14 05:29:26 +01:00			`meson`
pantheon: init a 5.0 2018-08-20 22:31:18 +02:00			`ninja`
pkgs/applications: pkgconfig -> pkg-config 2021-01-17 03:09:27 +01:00			`pkg-config`
spice-up: 1.8.2 -> 1.9.1 2022-01-14 05:29:26 +01:00			`python3`
pantheon: use latest vala elementary OS's ecosystem is curated around Ubuntu's LTS releases. This means the development platform for their curated applications always includes a LTS version of vala (in 18.04 it's 0.40). Because of how vala development works it suspect some of these applications to have serious issues if complied with the latest vala. However in the past year or so, for Pantheon at least, I don't think their applications will have much issues with latest vala, and if there is I don't think they'd be difficult to fix. In this single regard they've become more responsive since their preferred language is vala. As for the curated applications I have less of this confidence in. So I'd have to be accept less applications, but that's something I'm willing to compromise on. And this is easily reversible or could be done on a per-application basis. And nix already makes this trivial. 2019-10-10 04:47:37 +02:00			`vala`
pantheon: init a 5.0 2018-08-20 22:31:18 +02:00			`wrapGAppsHook`
spice-up: init at 1.2.1 2018-02-09 12:30:09 +01:00			`];`
spice-up: fix build with vala 0.46 See: https://github.com/Philip-Scott/Spice-up/pull/288 2019-10-14 22:33:03 +02:00
spice-up: init at 1.2.1 2018-02-09 12:30:09 +01:00			`buildInputs = [`
spice-up: 1.8.2 -> 1.9.1 2022-01-14 05:29:26 +01:00			`glib`
spice-up: 1.3.2 -> 1.6.0 2018-10-31 23:25:22 +01:00			`gtk3`
tree-wide: autorename gnome packages to use dashes 2018-02-25 03:23:58 +01:00			`json-glib`
spice-up: init at 1.2.1 2018-02-09 12:30:09 +01:00			`libevdev`
spice-up: 1.7.0 -> 1.8.0 2019-03-05 22:57:51 +01:00			`libgee`
spice-up: 1.3.2 -> 1.6.0 2018-10-31 23:25:22 +01:00			`libgudev`
			`libsoup`
spice-up: 1.8.2 -> 1.9.1 2022-01-14 05:29:26 +01:00			`pantheon.granite`
spice-up: init at 1.2.1 2018-02-09 12:30:09 +01:00			`];`

spice-up: 1.8.2 -> 1.9.1 2022-01-14 05:29:26 +01:00			`postPatch = ''`
			`chmod +x meson/post_install.py`
			`patchShebangs meson/post_install.py`
			`'';`
spice-up: fix build with vala 0.46 See: https://github.com/Philip-Scott/Spice-up/pull/288 2019-10-14 22:33:03 +02:00
treewide: pantheon updateScript 2019-12-23 00:19:30 +01:00			`passthru = {`
treewide: use nix-update updateScript for packages I maintain 2020-07-29 18:33:39 +02:00			`updateScript = nix-update-script {`
treewide: pantheon updateScript 2019-12-23 00:19:30 +01:00			`attrPath = pname;`
			`};`
			`};`

treewide: with stdenv.lib; in meta -> with lib; 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 2021-01-11 08:54:33 +01:00			`meta = with lib; {`
spice-up: 1.7.0 -> 1.8.0 2019-03-05 22:57:51 +01:00			`description = "Create simple and beautiful presentations";`
treewide: Per RFC45, remove all unquoted URLs 2020-04-01 03:11:51 +02:00			`homepage = "https://github.com/Philip-Scott/Spice-up";`
treewide: switch from pantheon.maintainers to lib.teams.pantheon 2021-09-18 17:00:51 +02:00			`maintainers = with maintainers; [ samdroid-apps xiorcale ] ++ teams.pantheon.members;`
spice-up: init at 1.2.1 2018-02-09 12:30:09 +01:00			`platforms = platforms.linux;`
			`# The COPYING file has GPLv3; some files have GPLv2+ and some have GPLv3+`
			`license = licenses.gpl3Plus;`
spice-up: 1.8.2 -> 1.9.1 2022-01-14 05:29:26 +01:00			`mainProgram = "com.github.philip_scott.spice-up";`
spice-up: init at 1.2.1 2018-02-09 12:30:09 +01:00			`};`
			`}`