Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 554564 - app-eselect/eselect-java: Use proper install location for current-user-vm
Summary: app-eselect/eselect-java: Use proper install location for current-user-vm
Status: CONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Java (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Java team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: eselect-java-tracker
  Show dependency tree
 
Reported: 2015-07-11 23:27 UTC by Manuel Rüger (RETIRED)
Modified: 2016-07-11 21:59 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Manuel Rüger (RETIRED) gentoo-dev 2015-07-11 23:27:54 UTC
VM_USER="${HOME}/.gentoo${EPREFIX}/java-config-2/current-user-vm"

Could this be replaced with VM_USER="${HOME}/.config/gentoo${EPREFIX}/java-config-2/current-user-vm" please?

This is the proper xdg location for that. :)
Comment 1 James Le Cuirot gentoo-dev 2015-07-12 05:44:51 UTC
eselect-java is due for other improvements so I'll lump this in.
Comment 3 William L. Thomson Jr. 2015-08-06 15:01:50 UTC
For jem, java-config port to C, I went with ~/.java/vm. Seemed to make a bit more sense, though it could go in ~/.config I guess.
Comment 4 James Le Cuirot gentoo-dev 2015-08-06 21:56:44 UTC
(In reply to Justin Lecher from comment #2)
> Has the fix already in there.

As discussed, this is not the same issue as the one you reported and the fix you mentioned was already present in 0.1.0. The issue was caused by a badly prepared tarball and -r1 now sources directly from gitweb instead.

I'll deal with the original issue in a new release along with other fixes.
Comment 5 James Le Cuirot gentoo-dev 2016-01-01 23:01:20 UTC
Crap, forgot about this for 0.2.0. Still, probably best to spread the disruption out a bit!
Comment 6 James Le Cuirot gentoo-dev 2016-07-11 21:59:25 UTC
Any bright ideas on how we could migrate this seamlessly? Doing writes in the module's global scope doesn't feel right.