-
-
Notifications
You must be signed in to change notification settings - Fork 15k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
texlive_latest: init at 2023.20230606 #236382
Draft
apfelkuchen6
wants to merge
14
commits into
NixOS:master
Choose a base branch
from
apfelkuchen6:nixpkgs-multi-version
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
b9d147b
texlive: move combinePkgs from default.nix to combine.nix
apfelkuchen6 f6fb151
texlive.combine: explicitly list params
apfelkuchen6 e2e1127
texlive: factor out tlpdb overrides
apfelkuchen6 60b9879
tests.texlive.fixedHashes: init
xworld21 dbbf86e
texlive: make scope
apfelkuchen6 15a2fb4
texlive: indent body of attrset
apfelkuchen6 10811c1
treewide: access texlive packages via texlive.pkgs instead of the top…
apfelkuchen6 711e366
texlive: extract generic interface
apfelkuchen6 8aaefd9
texlive: fix cross
apfelkuchen6 11f4310
luametatex: init at 2.10.08
apfelkuchen6 5506618
texlive: extract patches specific to texlive-2022 into stable.nix
apfelkuchen6 afdc12a
texlive: adjust generate-fixed-hashes for use with texlive_latest
apfelkuchen6 6d7b6f0
texlive.combine: prepare for texlive-2023
apfelkuchen6 ea56a00
texlive_latest: init at 2023.20230807
apfelkuchen6 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
{ stdenv, lib, fetchFromGitHub, cmake, ... }: | ||
stdenv.mkDerivation (finalAttrs: { | ||
pname = "luametatex"; | ||
version = "2.10.08"; | ||
|
||
src = fetchFromGitHub { | ||
owner = "contextgarden"; | ||
repo = "luametatex"; | ||
rev = "v${finalAttrs.version}"; | ||
hash = "sha256-KLRsJVzGyfbOfFSxUyT8mdxZ1Ud4EZrSxVB72i5jREU="; | ||
}; | ||
|
||
enableParallelBuilding = true; | ||
|
||
nativeBuildInputs = [ cmake ]; | ||
|
||
meta = with lib; { | ||
description = "minimal tex engine based on luatex"; | ||
homepage = "https://www.pragma-ade.nl/luametatex-1.htm"; | ||
license = licenses.gpl2Plus; | ||
maintainers = with lib.maintainers; [ apfelkuchen6 ]; | ||
}; | ||
}) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How hard would it be to have
bin.nix
as before, and an extrabin-latest.nix
with overrides only? Which I believe would be the more nixpkgs-y way of providing two versions.Alternatively,
bin-latest.nix
could be a straight copy ofbin.nix
, which would become the newbin.nix
once it becomes frozen.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Exactly as before is rather inconvenient as the sources would have to be overridden for every derivation. Just passing in the source as an argument and doing the patches and version-specific hacks via overrides shouldn't be too hard at this time as 2023 mostly just adds hacks over 2022. This might become more inconvenient if parts of hacks have to be removed.
I don't really like either approach. Using overrides makes upgrading less convenient and having a complete copy of the file feels really wasteful. I think just keeping
bin.nix
mostly general and put version-specific hacks/patches somewhere else for both versions is better as the upgrade remains just moving a file.