Confusion between Sub libraries and packages

[coot]

Consider a package which has a sublibrary cborg and also depend on cborg library published on Hackage, e.g.

library ...

library cborg
  build-depends: base,
                 cborg

In such setup I am getting an error since cabal confuses that the cborg sub-library and the Hackage one. I tried to fix this with this:

library ...

library cborg
  build-depends: base,
                 cborg:cborg

but it doesn't help. The only way I found to fix this is to change the sub-library name to x-cyborg - and now it doesn't clash with a published package name, but that's rather unfortunate. I'd expect sublibrary names to be independent namespace, so things like typed-protocols:cborg were possible (instead of rather lengthy typed-protocols:typed-protocols-cborg).

This should be fixed from another perspective. Consider one publishes a package which contains package:sublib, and in the future one publishes sublib to Hackage - which will break the already published package. From this perspective, I tend to think that all sublibraries should always be typed fully qualified, even in their own package. So in the example above, cborg would always mean the published Hackage package cborg, not the package:cborg sublibrary - if one wants that as a dependency, then package:cborg should be used.

[mpickering]

What is the error message you get? At which point are things confused?

[fgaz]

Seems like a duplicate of #6083. Try using cabal-version: 3.4

[fgaz]

This should be fixed from another perspective. Consider one publishes a package which contains package:sublib, and in the future one publishes sublib to Hackage - which will break the already published package. From this perspective, I tend to think that all sublibraries should always be typed fully qualified, even in their own package. So in the example above, cborg would always mean the published Hackage package cborg, not the package:cborg sublibrary - if one wants that as a dependency, then package:cborg should be used.

IIRC the sublibrary has precedence over other packages, so this shouldn't be an issue. From cabal-version 3.4 the qualified syntax is mandatory.

[coot]

@fgaz cabal-version: 3.4 indeed fixes it. Thanks!