Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 48384
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gnome Accessibility <gnome-accessibility@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Nicholas Jones (RETIRED) <carpaski@gentoo.org>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 48384 depends on: Show dependency tree
Bug 48384 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2004-04-19 12:08 0000 
QA Notice: java-config in global scope: app-accessibility/gnome-speech-0.3.2-r1

------- Comment #1 From foser (RETIRED) 2004-04-19 14:27:32 0000 ------- 
metadata carpaski.

------- Comment #2 From Leonardo Boshell (RETIRED) 2004-04-19 15:10:14 0000 ------- 
Thanks for the notice, but could you please try to provide a better description
of the problem?

Is it a scope problem? I mean, if I call java-config from a function then it's
correct? If so, could you please explain me why calling it from a global scope
is a bad thing?

I have a tentative -r2 which amongst other things replaces the java-config with
the $JDK_HOME var, which java-config provides anyway through the
/etc/env.d/XXjava entry. Is that a better approach?

Thanks.

------- Comment #3 From Leonardo Boshell (RETIRED) 2004-04-21 21:57:48 0000 ------- 
This should be resolved now.
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug