cafkafk/nixpkgs
cafkafk/nixpkgs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2
nixpkgs/pkgs/applications/misc/formatter/default.nix

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

80 lines
1.4 KiB
Nix
Raw Normal View History

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
{ lib, stdenv
formatter: init at 0.3.0
2019-10-06 11:40:23 +02:00
, fetchFromGitHub
treewide: use nix-update updateScript for packages I maintain
2020-07-29 18:33:39 +02:00
, nix-update-script
formatter: init at 0.3.0
2019-10-06 11:40:23 +02:00
, meson
, ninja
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
pkgs/applications: pkgconfig -> pkg-config
2021-01-17 03:09:27 +01:00
, pkg-config
formatter: init at 0.3.0
2019-10-06 11:40:23 +02:00
, pantheon
, python3
, substituteAll
, glib
, gtk3
, dosfstools
, e2fsprogs
, exfat
, hfsprogs
, ntfs3g
, libgee
, wrapGAppsHook
}:
stdenv.mkDerivation rec {
pname = "formatter";
formatter: 0.3.2 -> 0.4.0
2021-07-20 05:43:46 +02:00
version = "0.4.0";
formatter: init at 0.3.0
2019-10-06 11:40:23 +02:00
src = fetchFromGitHub {
owner = "Djaler";
repo = "Formatter";
rev = version;
formatter: 0.3.2 -> 0.4.0
2021-07-20 05:43:46 +02:00
sha256 = "sha256-8lZ0jUwHuc3Kntz73Btj6dJvkW2bvShu2KWTSQszbJo=";
formatter: init at 0.3.0
2019-10-06 11:40:23 +02:00
};
patches = [
(substituteAll {
src = ./fix-paths.patch;
ext4 = "${e2fsprogs}/bin/mkfs.ext4";
exfat = "${exfat}/bin/mkfs.exfat";
fat = "${dosfstools}/bin/mkfs.fat";
ntfs = "${ntfs3g}/bin/mkfs.ntfs";
hfsplus = "${hfsprogs}/bin/mkfs.hfsplus";
})
];
nativeBuildInputs = [
meson
ninja
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
pkgs/applications: pkgconfig -> pkg-config
2021-01-17 03:09:27 +01:00
pkg-config
formatter: init at 0.3.0
2019-10-06 11:40:23 +02:00
python3
wrapGAppsHook
];
buildInputs = [
glib
gtk3
libgee
pantheon.granite
];
postPatch = ''
chmod +x meson/post_install.py
patchShebangs meson/post_install.py
'';
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; {
formatter: init at 0.3.0
2019-10-06 11:40:23 +02:00
description = "A simple formatter designed for elementary OS";
homepage = "https://github.com/Djaler/Formatter";
treewide: switch from pantheon.maintainers to lib.teams.pantheon
2021-09-18 17:00:51 +02:00
maintainers = with maintainers; [ xiorcale ] ++ teams.pantheon.members;
formatter: init at 0.3.0
2019-10-06 11:40:23 +02:00
platforms = platforms.linux;
license = licenses.lgpl2Plus;
treewide: set meta.mainProgram for packages teams.pantheon.members maintain
2021-11-03 11:27:38 +01:00
mainProgram = "com.github.djaler.formatter";
formatter: init at 0.3.0
2019-10-06 11:40:23 +02:00
};
}
Reference in a new issue Copy permalink