| Summary: | Bad permissions don't let eclipse install new features | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Abraham Marin Perez <abraham> |
| Component: | [OLD] Development | Assignee: | Development Tools Team <dev-tools> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | centic, cgs, ikelos |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Abraham Marin Perez
2005-04-04 05:00:07 UTC
eclipse belongs to dev-tools In the examples above I used directories for eclipse-3, but same happens to eclipse-2. (In reply to comment #0) I would not recommend to change permissions of any directories. Would be better to run Eclipses Update Manager as root or (if possibly) use portage to keep your plugins up to date. changing the permissions or running eclipse as root is a bad idea a better way would be to add a default update site in $HOME, which i'm told is possible. I agree running Eclipse as root isn't a good idea and I don't think using portage's tree would be helpful since it would require a new ebuild for every available plug-in: the needed process to include a new ebuild in portage's tree may take some while, and managing it oneself would mean loosing it at every sync. I like portage's system, that's why I use Gentoo, but I think we shouldn't overload it whith plug-ins that could be managed fromt he application itself. I like the idea of using $HOME as the directory to where install plug-ins, but I guess it's a potential problem in a system with quotas. Seems like it might be a job for sudo, along with the right perms on the eclipse directories. I was thinking maybe an eclipse group with group perms, along with the appropriate sudo command(s). Others are much better with permissions than I (me science geek) so what do you all think? I think using sudo it's a good idea... A dependency should be added to eclipse but it will fix permissions problems while keeping files and directories in their right place. Futhermore, I think this solution may be extrapolated to other applications with similar problems, like Firefox and search engines, etc. What do developers think about it? Don't change any perms (certainly not to 0777!) Don't run anything as root, ever. That's just asking for trouble, and you usually get it. I just install the plugins into my home directory (~/eclipse or .eclipse), which is what everyone should probably do. If you have a quota and you run out, get a bigger one. If you install plugins as root, everyone will be subject to them, and they are very often broken. If other system users don't use those plugins, they will hurt them by wasting memory and whatever else the plugin happens to do that you don't need. (In reply to comment #6) > Seems like it might be a job for sudo, along with the right perms on the eclipse > directories. I was thinking maybe an eclipse group with group perms, along with > the appropriate sudo command(s). Others are much better with permissions than I > (me science geek) so what do you all think? I'm doing this but skipping sudo; instead just create the group and add myself to it, change group of /usr/lib/eclipse-3 & subdirs, set group writable. You should create an eclipse extention dir inside your $HOME and have it install there It's not a good idea to run it as root Short question: how do I add a different location for Eclipse plugins? Couldn't find it, the dialog in the update-manager doesn't allow me to add locations... (In reply to comment #11) > Short question: how do I add a different location for Eclipse plugins? Couldn't > find it, the dialog in the update-manager doesn't allow me to add locations... > It is possible to do such a thing, but it's true that it isn't like a permanent configuration issue whatsoever. When you are installing a new plugin and you have already gone through the first "preparation" steps (selecting/adding the remote site, chosing version, accepting license, etc.) you'll arrive at the "install location" window; there you can choose one of the default installation sites or specify a new installation site. Press the "add site" button, choose a directory for your plugins and you'll be done. From now on, the installation site you created will appear once you are in this window, so you'll be able to install all your plugins there. HTH The Eclipse-3.2 sdk allows you to install plugins locally. Is that an ok resolution to this bug? Yes. This really isn't a bug at all. (In reply to comment #14) > Yes. This really isn't a bug at all. > Well, it WAS a bug the day it was reported, don't be confused by the fact that after more than one year messing around with this topic the solution seems quite clear. Now, if no one disagrees, I'll mark this bug as fixed. This "bug" had the exact same solution back then, as I posted on 2005-06-30. :) (In reply to comment #16) > This "bug" had the exact same solution back then, as I posted on 2005-06-30. :) > Yes, that's totally true, although you didn't really say how to fix this problem; you mentioned the solution, but forgot to say how to apply it ;-). Proof of this is that on 2006-04-23 people were still working on that (see comment #11). Anyhow, the good news are that now the whole thing is over and everyone will be able to install new feauters through Eclipse's Update Manager flawlessly. And that's good for all us, isn't it? :) |
