| Summary: | emerge tora 1.3.16 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Andreas Wuest <KickMeToAndy> |
| Component: | Current packages | Assignee: | Don Seiler (RETIRED) <rizzo> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Andreas Wuest
2005-03-25 01:25:35 UTC
Do you not have Oracle and therefore not have the $ORACLE_HOME env var set? with all the previous version i never had and a problem running the emerge. i do not have oracle and i do not have set an $ORACLE_HOME variable(now and then). i use tora to access my postgresql database. that hint with the oracle home variable was really good. i just had to set it with a dummy value and the emerge worked! should be somehow documented that the oracle home variable has to be set, even if you do not have an oracle application -> is it possible to let the emerge check if a oracle home var exists, if not, export one for the current shell with a dummy value (e.g./tmp) before building tora, so the emerge does not fail ?? A little searching goes a long way. As I said in the bug that this is a dupe of, the problem is known upstream and will be fixed in their next version. I'm waiting for a reply on the dev list for an ETA. As for the ebuild exporting a dummy ORACLE_HOME, yes that _would_ solve the build, but then I'd need to alter the /usr/bin/tora script as well. Depending on when the ETA for the next release is, I'll think about it. *** This bug has been marked as a duplicate of 85646 *** |