Herbert Valerio Riedel

> I went to install hopenssl today, and the flags were ignored completely. They are *not* completely ignored; they currently only apply to local packages (i.e. locally unpacked ones e.g.)...

> The problem is that v2-build and v2-install flags have do the same things, otherwise one consider that inconsistency a bug. I'd be worth articulating why exactly; For one, `cabal...

nevermind; disregard the comment below -- I misunderstood your report at first ---- @mrkkrp Btw, `cabal new-build` w/o any target is context-specific (i.e. CWD specific;similar to how `make` works) iow,...

@mrkkrp ok, here's what's going on: the target `megaparsec` refers to the library component of `megaparsec`, not to the *package* `megaparsec` in other words, the statement ``` cabal new-build megaparsec...

@mrkkrp you're right; something's inconsistent here; the target doesn't seem to be resolved the way I described it... needs more investigation

I suspect that the `hasValidHaddockTargets` predicate in 338c3581db7b83686ce67c6ff9aec0b10cf50f56 might need some tweaking... cc @typedrat

...at the risk of stating the obvious, have you tried already with `apt-get install libtinfo-dev` ?

@23Skidoo relevant: https://github.com/haskell/cabal/issues/3581

Isn't this basically the conversion to/from ShortByteString? If I understand it correctly, `ByteArray` is the same as ``` data ShortByteString = SBS ByteArray# ``` (slightly related, in the past I...

But do we want to keep referring to `v2-build` forever? I assumed we'd phase out the term `v2-build` to become `cabal build`, at which point referring to it as `v2-build`...