bioconda / bioconda-recipes Public
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
Trinity: need to remove @ from paths in perl script
#14466
Comments
|
Is this a Bioconda issue (packaging) or an upstream problem at Trinity (software)? ping @bgruening - if this is galaxy specific, maybe you know who could help. |
|
Kind of both: The cause of the problem is that galaxy uses an If perl packages/programs use hard coded paths (e.g. via an install script that uses BIN_DIR as parameter) for dependencies, then the perl interpreter has problems in this case since the @ should be quoted. One solution is to remove the hard coded paths (which I did for stacks) since the binaries are on the PATH anyway. Alternatively the @ could be quoted. Don't know if conda could do this in general for BIN_DIR (or all its path). |
|
So basically, you are saying that |
|
I'm no perl expert, but |
|
@msarahan Can you pitch in with suggestions here? From So installing into an env with Do you have code handling this for bash? Is there a chance to add code to |
|
no, I don't think we have anything for that currently. A PR to add it would be welcome. |
|
Quick pointer where it would have to go? (term that can be |
|
@bernt-matthias For the time being, can you come up with a patch for Trinity? Using |
|
(Or use |
|
I've created an issue for now (conda/conda#8601), adding to the nearly 1k open ones over there. |
|
done #14741 |
Happens within Galaxy which uses the @ character in the environment names.
Error is:
Had the same problem in the stacks2 wrapper. For variables setting path to binaries that are on the PATH anyway the solution is to set them to an empty string.
For the others (like paths to jar files), a fix might involve using some
pwdmagic.The text was updated successfully, but these errors were encountered: