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

{ lib
, stdenv
, fetchFromGitHub
, nix-update-script
, pantheon
, pkg-config
, vala
, cmake
, ninja
, gtk3
, gtksourceview3
, webkitgtk
, gtkspell3
, glib
, libgee
, pcre
, sqlite
, discount
, wrapGAppsHook
, withPantheon ? false
}:

stdenv.mkDerivation rec {
  pname = "notes-up";
  version = "unstable-2020-12-29";

  src = fetchFromGitHub {
    owner = "Philip-Scott";
    repo = "Notes-up";
    rev = "2ea9f35f588769758f5d2d4436d71c4059141a6f";
    sha256 = "sha256-lKOM9+s34xYB9bF9pgip9DFu+6AaxSE4HjFVhoWtttk=";
  };

  nativeBuildInputs = [
    cmake
    ninja
    vala
    pkg-config
    wrapGAppsHook
  ];

  buildInputs = [
    discount
    glib
    gtk3
    gtksourceview3
    gtkspell3
    libgee
    pantheon.granite
    pcre
    sqlite
    webkitgtk
  ];

  # Whether to build with contractor support (Pantheon specific)
  cmakeFlags = lib.optional (!withPantheon) "-Dnoele=yes";

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

  meta = with lib; {
    description = "Markdown notes editor and manager designed for elementary OS"
      + lib.optionalString withPantheon " - built with Contractor support";
    homepage = "https://github.com/Philip-Scott/Notes-up";
    license = licenses.gpl2Only;
    maintainers = with maintainers; [ ] ++ teams.pantheon.members;
    platforms = platforms.linux;
    mainProgram = "com.github.philip-scott.notes-up";
  };
}
pantheon.notes-up: 2.0.2 -> unstable-2020-12-29 (#128316) 2021-06-30 01:22:36 +00:00			`{ lib`
			`, stdenv`
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 02:47:37 +00:00			`, fetchFromGitHub`
treewide: use nix-update updateScript for packages I maintain 2020-07-29 16:33:39 +00:00			`, nix-update-script`
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 02:47:37 +00:00			`, pantheon`
pkgs/applications: pkgconfig -> pkg-config 2021-01-17 02:09:27 +00:00			`, pkg-config`
pantheon.notes-up: 2.0.2 -> unstable-2020-12-29 (#128316) 2021-06-30 01:22:36 +00:00			`, vala`
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 02:47:37 +00:00			`, cmake`
			`, ninja`
			`, gtk3`
			`, gtksourceview3`
			`, webkitgtk`
			`, gtkspell3`
			`, glib`
			`, libgee`
pantheon.notes-up: 2.0.2 -> unstable-2020-12-29 (#128316) 2021-06-30 01:22:36 +00:00			`, pcre`
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 02:47:37 +00:00			`, sqlite`
			`, discount`
			`, wrapGAppsHook`
pantheon.notes-up: 2.0.2 -> unstable-2020-12-29 (#128316) 2021-06-30 01:22:36 +00:00			`, withPantheon ? false`
			`}:`
notes-up: init at 1.6.3 2019-02-05 20:34:54 +00:00
			`stdenv.mkDerivation rec {`
			`pname = "notes-up";`
pantheon.notes-up: 2.0.2 -> unstable-2020-12-29 (#128316) 2021-06-30 01:22:36 +00:00			`version = "unstable-2020-12-29";`
notes-up: init at 1.6.3 2019-02-05 20:34:54 +00:00
			`src = fetchFromGitHub {`
			`owner = "Philip-Scott";`
			`repo = "Notes-up";`
pantheon.notes-up: 2.0.2 -> unstable-2020-12-29 (#128316) 2021-06-30 01:22:36 +00:00			`rev = "2ea9f35f588769758f5d2d4436d71c4059141a6f";`
			`sha256 = "sha256-lKOM9+s34xYB9bF9pgip9DFu+6AaxSE4HjFVhoWtttk=";`
notes-up: init at 1.6.3 2019-02-05 20:34:54 +00:00			`};`

			`nativeBuildInputs = [`
			`cmake`
			`ninja`
pantheon.notes-up: 2.0.2 -> unstable-2020-12-29 (#128316) 2021-06-30 01:22:36 +00:00			`vala`
pkgs/applications: pkgconfig -> pkg-config 2021-01-17 02:09:27 +00:00			`pkg-config`
notes-up: init at 1.6.3 2019-02-05 20:34:54 +00:00			`wrapGAppsHook`
			`];`

			`buildInputs = [`
			`discount`
			`glib`
			`gtk3`
			`gtksourceview3`
			`gtkspell3`
			`libgee`
			`pantheon.granite`
pantheon.notes-up: 2.0.2 -> unstable-2020-12-29 (#128316) 2021-06-30 01:22:36 +00:00			`pcre`
notes-up: init at 1.6.3 2019-02-05 20:34:54 +00:00			`sqlite`
			`webkitgtk`
			`];`

notes-up: default without pantheon support This adds pantheon.notes-up which will only work in pantheon. 2019-02-22 18:45:57 +00:00			`# Whether to build with contractor support (Pantheon specific)`
pkgs/applications: stdenv.lib -> lib 2021-01-15 05:42:41 +00:00			`cmakeFlags = lib.optional (!withPantheon) "-Dnoele=yes";`
notes-up: default without pantheon support This adds pantheon.notes-up which will only work in pantheon. 2019-02-22 18:45:57 +00:00
treewide: pantheon updateScript 2019-12-22 23:19:30 +00:00			`passthru = {`
treewide: use nix-update updateScript for packages I maintain 2020-07-29 16:33:39 +00:00			`updateScript = nix-update-script {`
treewide: pantheon updateScript 2019-12-22 23:19:30 +00: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 07:54:33 +00:00			`meta = with lib; {`
notes-up: default without pantheon support This adds pantheon.notes-up which will only work in pantheon. 2019-02-22 18:45:57 +00:00			`description = "Markdown notes editor and manager designed for elementary OS"`
pantheon.notes-up: 2.0.2 -> unstable-2020-12-29 (#128316) 2021-06-30 01:22:36 +00:00			`+ lib.optionalString withPantheon " - built with Contractor support";`
notes-up: use older vala to fix build Looks unresolved upstream: https://github.com/Philip-Scott/Notes-up/issues/349 2020-03-19 14:43:32 +00:00			`homepage = "https://github.com/Philip-Scott/Notes-up";`
pantheon.notes-up: 2.0.2 -> unstable-2020-12-29 (#128316) 2021-06-30 01:22:36 +00:00			`license = licenses.gpl2Only;`
pantheon: add maintainers team 2021-08-02 00:46:24 +00:00			`maintainers = with maintainers; [ ] ++ teams.pantheon.members;`
notes-up: init at 1.6.3 2019-02-05 20:34:54 +00:00			`platforms = platforms.linux;`
treewide: set meta.mainProgram for packages teams.pantheon.members maintain 2021-11-03 10:27:38 +00:00			`mainProgram = "com.github.philip-scott.notes-up";`
notes-up: init at 1.6.3 2019-02-05 20:34:54 +00:00			`};`
			`}`