Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ability to suppress extra-src-files relative path warning #5581

Closed
chshersh opened this issue Sep 18, 2018 · 2 comments
Closed

Add ability to suppress extra-src-files relative path warning #5581

chshersh opened this issue Sep 18, 2018 · 2 comments

Comments

@chshersh
Copy link
Member

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!

@hvr
Copy link
Member

hvr commented Sep 18, 2018

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.

@ffaf1
Copy link
Collaborator

ffaf1 commented Jan 10, 2024

With #9442 you can now do it.

@ffaf1 ffaf1 closed this as completed Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants