followup
This commit is contained in:
parent
f203475eae
commit
df7d8dbd08
2 changed files with 13 additions and 0 deletions
|
@ -1 +1,3 @@
|
||||||
Not sure it's a bug, but the networkbsd flag defaults to true in git-annex.cabal and to false in stack.yaml -- is that intended?
|
Not sure it's a bug, but the networkbsd flag defaults to true in git-annex.cabal and to false in stack.yaml -- is that intended?
|
||||||
|
|
||||||
|
> not a bug, [[done]] --[[Joey]]
|
||||||
|
|
|
@ -0,0 +1,11 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="joey"
|
||||||
|
subject="""comment 1"""
|
||||||
|
date="2020-03-16T17:14:20Z"
|
||||||
|
content="""
|
||||||
|
Yes. When cabal is used, it will unset the flag as
|
||||||
|
necessary if an older version of network is available. Meanwhile,
|
||||||
|
stack uses lts-14.27, which includes network-2.x, and somehow stack
|
||||||
|
forces the networkbsd flag to not be unset in that case. (I don't know
|
||||||
|
how/why.)
|
||||||
|
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue