| Age | Commit message (Collapse) | Author |
|---|
|
Upstream has updated resolver, so the previous settings were a downgrade
|
|
|
|
Since pandoc (the project) has split (a while back, actually) into the
cli and other components, the vanilla package name for the dependency
has changed to suit. Use that for the dependency name.
Also, it suffices to conflict against the vanilla package, as all the
variant packages should provide=(pandoc-cli) which will make them
conflict with us given we conflicts=(pandoc-cli).
|
|
Note: I changed the indentation style, this commit is best viewed with
--ignore-all-space
|
|
|
|
One thing that *does* need massaging in upstream versioning is their use
of -rc releases. Luckily, vercmp sorts 3.2rc < 3.2, so all that's needed
is to strip the illegal characters.
(Although, in testing this I've just discovered upstream has deleted the
3.2-rc tag, so perhaps this'll end up being unnecessary)
Punting on also stripping colons, slashes and whitespace until
necessary.
|
|
There's no need to second-guess upstream versioning -- we shouldn't be
covering for upstream sometimes tagging releases a couple commits after
they've bumped it in the cabal file.
|
|
|
|
Although correct, this was breaking some automated tooling, and is
unnecessary regardless
|
|
Transitive deps of extra/pandoc, so we need to pull them in explicitly.
|
|
The default makepkg configuration sets LDFLAGS but not LD.
GHC used to take this as its cue to select its own choice of LD.
However GHC would *not* check that its choice of LD supports LDFLAGS.
This is a problem for dependencies with C components, which get linked
using this LD.
A fix[1] for this has landed in ghc 9.6.5 on 2024-04-16, and ghc's
installed using the current ghcup HEAD (starting with 7a684ad[2]) will
have `--disable-ld-override` passed, which also fixes the issue.
[1] - https://gitlab.haskell.org/ghc/ghc/-/issues/24565
[2] - https://github.com/haskell/ghcup-hs/issues/1032
|
|
Thanks to @alerque for reminding me of the makedep requirement
|
|
.gitattributes are useful for local configuration, but they shouldn't
have been checked in
|
|
Cf discussion in https://github.com/jgm/pandoc/issues/9248.
Given upstream preferences in re workflow, this is the best we can do to
signal version bump breakage
|
|
Obsolete for two years already, cf 2415b26
|
|
|
|
|
|
|
|
Deprecated since pandoc absorbed it as a library on 2020-09-06 in
e0984a43a99231e72c02a0a716c8d0315de9abdf
|
|
Upstream accepted the patch
|
|
Commits 3692a1d..c5287e9 introduce a dependency on pandoc-lua-marshal
0.1.0.1
However, this bound change was only reflected in stack.yaml, not
pandoc.cabal
For some reason stack.yaml isn't picked up by `stack build`, so this
breaks the build
Reported upstream as https://github.com/jgm/pandoc/issues/7721
|
|
Previous config also killed diffs
|
|
|
|
|