-
Notifications
You must be signed in to change notification settings - Fork 213
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
Support all phases supported by cpanfile #502
Comments
|
My use case: I want to install all dependencies except the dependencies required by my test suite. So in development build I would run:
and in production:
This means my production build is slightly smaller. |
You just run |
Oh, I guess it will still install the test group. It came up as a requirement from Travis CI when they want to skip testing the dependencies but still needs to install the |
I faced the same problem as evoyy. cpanfile would be much more precise if I could put dependencies where they really belong. Currently, I have to stash test dependencies in develop for Travis to work and it is confusing for they do not belong in develop. |
cpanfile specifies:
However, cpanm only provides switches for configure and develop phases:
Will it be possible to install dependencies for the other phases (build, test, runtime)? I was expecting to find a switch
--with-test
.The text was updated successfully, but these errors were encountered: