You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently structure of my project looks very similar to the following one:
haskell/
frontend/
mobile/
proto/
The directory proto contains Protocol Buffers description of messages. To keep track of those files in my project I put those files under extra-source-files field in the haskell/my-project.cabal file. But because of that I see a lot of warnings like this one:
Warning: 'extra-src-files:../proto/common.proto' is a relative path
outside of the source tree.This will not work when generating a tarball with
'sdist'.
Since I'm not going to publish project to Hackage, I would like to suppress this warning and reduce noise in the output. Thanks!
The text was updated successfully, but these errors were encountered:
Relatedly, I've got a spec draft bitrotting in my INBOX describing "cabal profiles" (name loosely inspired by the concept of MPEG profiles) which you can use to declare the level of strictness your package description needs to meet (depending on whether you intend to distribute the package to Hackage which has fairly strict portability & policy requirements, or whether this is an inhouse package which only needs to be portable across Unix environments etc), and which would affect the warnings emitted by cabal & cabal check, as well as serve as a safe-guard against accidentally publishing a package to Hackage.
Currently structure of my project looks very similar to the following one:
The directory
proto
contains Protocol Buffers description of messages. To keep track of those files in my project I put those files underextra-source-files
field in thehaskell/my-project.cabal
file. But because of that I see a lot of warnings like this one:Since I'm not going to publish project to Hackage, I would like to suppress this warning and reduce noise in the output. Thanks!
The text was updated successfully, but these errors were encountered: