nordic-dev.net/nixpkgs
nordic-dev.net/nixpkgs
2
0
Fork 0
mirror of https://github.com/NixOS/nixpkgs.git synced 2024-12-27 16:15:05 +00:00
Code Issues Packages Projects Releases Wiki Activity
bf5eb87033
nixpkgs/pkgs/applications/networking/browsers/next/default.nix

96 lines
2.0 KiB
Nix
Raw Normal View History

next: Fix #74258 Next had a few issues with its packaging: * the platform port was exposed in all-packages And this is not useful for outside users. It's now a local attribute in the next package. * the platform port wasn't wrapped correctly It appears that the lisp core was being wrapped, when instead the actual gtk application that's called within the lisp core had to be wrapped. * codestyle/indentation
2019-11-26 13:25:12 +00:00
{ stdenv
, fetchFromGitHub
next: init at 1.3.1
2019-09-10 20:16:33 +00:00
, lispPackages
, sbcl
next: Fix #74258 Next had a few issues with its packaging: * the platform port was exposed in all-packages And this is not useful for outside users. It's now a local attribute in the next package. * the platform port wasn't wrapped correctly It appears that the lisp core was being wrapped, when instead the actual gtk application that's called within the lisp core had to be wrapped. * codestyle/indentation
2019-11-26 13:25:12 +00:00
, callPackage
next: init at 1.3.1
2019-09-10 20:16:33 +00:00
}:
next: Fix #74258 Next had a few issues with its packaging: * the platform port was exposed in all-packages And this is not useful for outside users. It's now a local attribute in the next package. * the platform port wasn't wrapped correctly It appears that the lisp core was being wrapped, when instead the actual gtk application that's called within the lisp core had to be wrapped. * codestyle/indentation
2019-11-26 13:25:12 +00:00
let
# This is the wrapped webkitgtk platform port that we hardcode into the Lisp Core.
# See https://github.com/atlas-engineer/next/tree/master/ports#next-platform-ports
next-gtk-webkit = callPackage ./next-gtk-webkit.nix {};
next: init at 1.3.1
2019-09-10 20:16:33 +00:00
next: Fix #74258 Next had a few issues with its packaging: * the platform port was exposed in all-packages And this is not useful for outside users. It's now a local attribute in the next package. * the platform port wasn't wrapped correctly It appears that the lisp core was being wrapped, when instead the actual gtk application that's called within the lisp core had to be wrapped. * codestyle/indentation
2019-11-26 13:25:12 +00:00
in
stdenv.mkDerivation rec {
pname = "next";
next: 1.4.0 -> 1.5.0
2020-03-09 17:50:34 +00:00
version = "1.5.0";
next: init at 1.3.1
2019-09-10 20:16:33 +00:00
next: Fix #74258 Next had a few issues with its packaging: * the platform port was exposed in all-packages And this is not useful for outside users. It's now a local attribute in the next package. * the platform port wasn't wrapped correctly It appears that the lisp core was being wrapped, when instead the actual gtk application that's called within the lisp core had to be wrapped. * codestyle/indentation
2019-11-26 13:25:12 +00:00
src = fetchFromGitHub {
owner = "atlas-engineer";
repo = "next";
rev = version;
next: 1.4.0 -> 1.5.0
2020-03-09 17:50:34 +00:00
sha256 = "1gqkp185wcwaxr8py90hqk44nqjblrrdwvig19gizrbzr2gx2zhy";
next: Fix #74258 Next had a few issues with its packaging: * the platform port was exposed in all-packages And this is not useful for outside users. It's now a local attribute in the next package. * the platform port wasn't wrapped correctly It appears that the lisp core was being wrapped, when instead the actual gtk application that's called within the lisp core had to be wrapped. * codestyle/indentation
2019-11-26 13:25:12 +00:00
};
next: init at 1.3.1
2019-09-10 20:16:33 +00:00
next: Fix #74258 Next had a few issues with its packaging: * the platform port was exposed in all-packages And this is not useful for outside users. It's now a local attribute in the next package. * the platform port wasn't wrapped correctly It appears that the lisp core was being wrapped, when instead the actual gtk application that's called within the lisp core had to be wrapped. * codestyle/indentation
2019-11-26 13:25:12 +00:00
nativeBuildInputs = [
sbcl
] ++ (with lispPackages; [
prove-asdf
trivial-features
]);
next: init at 1.3.1
2019-09-10 20:16:33 +00:00
next: Fix #74258 Next had a few issues with its packaging: * the platform port was exposed in all-packages And this is not useful for outside users. It's now a local attribute in the next package. * the platform port wasn't wrapped correctly It appears that the lisp core was being wrapped, when instead the actual gtk application that's called within the lisp core had to be wrapped. * codestyle/indentation
2019-11-26 13:25:12 +00:00
buildInputs = with lispPackages; [
alexandria
bordeaux-threads
cl-annot
cl-ansi-text
cl-css
cl-json
cl-markup
cl-ppcre
cl-ppcre-unicode
cl-prevalence
closer-mop
dbus
dexador
ironclad
local-time
log4cl
lparallel
mk-string-metrics
parenscript
next: 1.3.4 -> 1.4.0
2020-02-06 04:18:59 +00:00
plump
next: Fix #74258 Next had a few issues with its packaging: * the platform port was exposed in all-packages And this is not useful for outside users. It's now a local attribute in the next package. * the platform port wasn't wrapped correctly It appears that the lisp core was being wrapped, when instead the actual gtk application that's called within the lisp core had to be wrapped. * codestyle/indentation
2019-11-26 13:25:12 +00:00
quri
next: 1.3.4 -> 1.4.0
2020-02-06 04:18:59 +00:00
serapeum
next: Fix #74258 Next had a few issues with its packaging: * the platform port was exposed in all-packages And this is not useful for outside users. It's now a local attribute in the next package. * the platform port wasn't wrapped correctly It appears that the lisp core was being wrapped, when instead the actual gtk application that's called within the lisp core had to be wrapped. * codestyle/indentation
2019-11-26 13:25:12 +00:00
sqlite
str
swank
trivia
trivial-clipboard
next: 1.3.4 -> 1.4.0
2020-02-06 04:18:59 +00:00
trivial-types
next: Fix #74258 Next had a few issues with its packaging: * the platform port was exposed in all-packages And this is not useful for outside users. It's now a local attribute in the next package. * the platform port wasn't wrapped correctly It appears that the lisp core was being wrapped, when instead the actual gtk application that's called within the lisp core had to be wrapped. * codestyle/indentation
2019-11-26 13:25:12 +00:00
unix-opts
];
next: 1.3.1 -> 1.3.4
2019-10-10 07:39:48 +00:00
next: set next-gtk-webkit as a propagated build input Because this reference is unfortunately not detected by Nix. Fixes #76834.
2020-01-02 20:26:38 +00:00
# This reference is unfortunately not detected by Nix
propagatedBuildInputs = [ next-gtk-webkit ];
next: Fix #74258 Next had a few issues with its packaging: * the platform port was exposed in all-packages And this is not useful for outside users. It's now a local attribute in the next package. * the platform port wasn't wrapped correctly It appears that the lisp core was being wrapped, when instead the actual gtk application that's called within the lisp core had to be wrapped. * codestyle/indentation
2019-11-26 13:25:12 +00:00
prePatch = ''
substituteInPlace source/ports/gtk-webkit.lisp \
--replace "next-gtk-webkit" "${next-gtk-webkit}/bin/next-gtk-webkit"
'';
next: init at 1.3.1
2019-09-10 20:16:33 +00:00
next: Fix #74258 Next had a few issues with its packaging: * the platform port was exposed in all-packages And this is not useful for outside users. It's now a local attribute in the next package. * the platform port wasn't wrapped correctly It appears that the lisp core was being wrapped, when instead the actual gtk application that's called within the lisp core had to be wrapped. * codestyle/indentation
2019-11-26 13:25:12 +00:00
buildPhase = ''
common-lisp.sh --eval "(require :asdf)" \
--eval "(asdf:load-asd (truename \"next.asd\") :name \"next\")" \
--eval '(asdf:make :next)' \
--quit
'';
next: init at 1.3.1
2019-09-10 20:16:33 +00:00
next: Fix #74258 Next had a few issues with its packaging: * the platform port was exposed in all-packages And this is not useful for outside users. It's now a local attribute in the next package. * the platform port wasn't wrapped correctly It appears that the lisp core was being wrapped, when instead the actual gtk application that's called within the lisp core had to be wrapped. * codestyle/indentation
2019-11-26 13:25:12 +00:00
installPhase = ''
install -D -m0755 next $out/bin/next
'';
next: init at 1.3.1
2019-09-10 20:16:33 +00:00
next: Fix #74258 Next had a few issues with its packaging: * the platform port was exposed in all-packages And this is not useful for outside users. It's now a local attribute in the next package. * the platform port wasn't wrapped correctly It appears that the lisp core was being wrapped, when instead the actual gtk application that's called within the lisp core had to be wrapped. * codestyle/indentation
2019-11-26 13:25:12 +00:00
# Stripping destroys the generated SBCL image
dontStrip = true;
next: init at 1.3.1
2019-09-10 20:16:33 +00:00
next: Fix #74258 Next had a few issues with its packaging: * the platform port was exposed in all-packages And this is not useful for outside users. It's now a local attribute in the next package. * the platform port wasn't wrapped correctly It appears that the lisp core was being wrapped, when instead the actual gtk application that's called within the lisp core had to be wrapped. * codestyle/indentation
2019-11-26 13:25:12 +00:00
meta = with stdenv.lib; {
description = "Infinitely extensible web-browser (with Lisp development files using WebKitGTK platform port)";
homepage = https://next.atlas.engineer;
license = licenses.bsd3;
maintainers = [ maintainers.lewo ];
platforms = [ "x86_64-linux" ];
};
}
Reference in New Issue Copy Permalink