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
[enhancement] "apt" addon lacks "apt-get build-dep" binding #4710
Comments
This seems like a handy idea to me. Is it acceptable to use the existing allowed packages list for purposes of allowing |
Woops, I didn't realise this question was for me (ie, that you actually are part of travis-ci). I am not too familiar with the package list, but it makes sense to allow building any package which is already allowed in binary form, if that's what it means. |
The absence of this prevents me from using the container infrastructure in some builds. |
Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues |
I found this issue while trying to do exactly what OP was asking for. I'd vote for re-opening. (Is that how this works?) |
apt-get build-dep is a nice way to get most build-dependencies for a package. When one needs testing more than one version of a third-party dependency, this helps a lot.
Please extend "apt" add-on with a container-friendly equivalent to "apt-get build-dep".
The text was updated successfully, but these errors were encountered: