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.

Sign up for GitHub

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

Jump to bottom

tainted not working with vendored modules #3

Open
ale-rinaldi opened this issue Jun 11, 2020 · 0 comments · May be fixed by #4
Open

tainted not working with vendored modules #3

ale-rinaldi opened this issue Jun 11, 2020 · 0 comments · May be fixed by #4

Comments

@ale-rinaldi
Copy link

When running tainted using vendored modules, there is no way to specify the vendor folder to look for modules into.
Instead, it tries to download them again, eventually failing if some of them is private or unreachable.

This seems to be a limitation of the build module, and it's suggested to switch to the packages module to fix this.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Switch to packages module, allow to specify mod folder criptalia/tainted
1 participant
@ale-rinaldi