Bugzilla – Full Text Bug Listing
| Summary: | [plan item] Improve organizational control over product updates | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Jim des Rivieres <jeem> |
| Component: | Update (deprecated - use Eclipse>Equinox>p2) | Assignee: | Dorian Birsan <birsan> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P4 | CC: | danjou, ed.burnette, eric.estievenart, gunnar, jasc, konradk, lbarnhil, m.a.r.k, manahan |
| Version: | 2.1 | Keywords: | plan |
| Target Milestone: | 3.0 M3 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Jim des Rivieres
Is this also including support for keeping parts of eclipse under the control of Package manager (-> dpkg, rpm) or just generally a root user? See bug#36101 for my problems with that. Don't know if this topic would fit better into bug#37692 or bug#37688 ... *** Bug 36755 has been marked as a duplicate of this bug. *** Initial version of command line tool for mirroring features from remote update site has been released (into HEAD). The parameters are documented http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-update- home/doc/working/documentation/standalone_update.html for now. The proposal for automatic updates described at http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update- home/doc/working/update-policy.html. Also, please refer to the link mentioned by Konrad for how to use the site mirroring utility. has been implemented, so I will mark this as fixed. Feel free to provide feedback by adding comments to this bug, or open new bugs to address any issues. Will it be possible to exclude parts (all in my case, as my eclipse installation is handled by the debian package manager) of eclipse from being updated via update-manager? Jan, There a few things left unspecified in the proposal mentioned above, so I'd suggest we implement the following: 1. when the "url" attribute is an empty string "" then assume that features matching the specified pattern are not updatable 2. when the "pattern" attribute is "*" then all features that don't match any pattern will be matched to this rule. Now, the policy file you need to have so no feature will ever be updated is: <update-policy> <url-map pattern="*" url=""/> </update-policy> Does this look ok ? Yes, that would be great. What will the update manager say, when a users tries to update such a 'site'? Or will it be 'greyed out'? One thing would be nice, if you could overwrite such a setting with the comandline updatemanager. Usecase would be, that the admin of a box will update features in /usr/local. This site shouldn't be updateable by a normal user, but only by the local admin. Thanks again for this feature, this will make my life as debian eclipse maintainer a lot easier. I have released the poposed changes for the next build.
I sense a bit of misunderstanding about proxy (policy) files and updatability
of sites: the proxy files is really a redirection mechanism for the location
of updates. This mechanism is not a strict enforcement, but requires user's
compliance.
So, when using the policy file, if the url is empty, features would not be
able to be updated using the Find and Install wizard by selecting the first
option ("Search for updates for the currently installed features").
One can still install new features using the same wizard, but selecting the
second option ("Search for new features to install").
My understanding of your scenario is this:
- the admin install eclipse in /usr/local (under the admin account)
- other users launch this eclipse from their own accounts and do not have
write access to the /usr/local directory
- the admin provides a policy.xml (or whatever name) in /usr/local and each
user would have to manually enter it on the preference page
- the admin has write access to /usr/local, so he can always install new
features or update existing ones, but users will not be able to update their
features (of course, assuming they run with the proper preference settings).
My 'problem' goes even a bit deeper: Eclipse is installed in /usr/share/eclipse via apt-get/dpkg (debian package manager). It is setup and patched (see bug#36101) to include the site /usr/local/share/eclipse (via links/usr_local.links) and user added sites (in $HOME, added by the patch). Basicly the policy for this sites (as used internaly by PlatformConfiguration) is * /usr/share/eclipse is a no-no, as it is package manager controled (ensured by a patch) * /usr/local/share/eclipse should only be updatebale by root. Ensured by using internal 'path=r /usr/local/share'. This are for plugins, which are not packaged and which should be updated only by root via the comandline updater (which I will package when I've done 3.0). * Sites in $HOME should be updateable by the user (currently (2.1.1) not possible because update-manager doesn't show this sites -> bug#39890). Jan We could use that patch (from comment #9); has it been posted anywhere? Just uploaded the latest version to bug#36101 *** Bug 59382 has been marked as a duplicate of this bug. *** |