Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 341813 - [eclipse-build] Move away from dropins
Summary: [eclipse-build] Move away from dropins
Status: CLOSED WONTFIX
Alias: None
Product: Linux Tools
Classification: Tools
Component: eclipse-build (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 1.0   Edit
Assignee: Packaging Tools Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-04 11:55 EDT by Andrew Overholt CLA
Modified: 2013-01-10 12:28 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Overholt CLA 2011-04-04 11:55:46 EDT 
We should stop using dropins for jdt, pde, cdt, etc. and use the p2 director.  Doing this will require us to advise Linux distributions on how best to install things on top of the platform and allow for graceful addition/removal of such plugins/features.  Requirements include:

- single copy of bundles on disk (as layed down by the RPM or .deb or whatever)
- system (RPM, DEB, etc.) must manage file addition/removal
- end users must still be able to install things on top of the system-wide installation but the shared installation should trump any user-installed content; IOW:  Eclipse should *always* start
- any calls to the director must touch a minimal # of files on disk and those should be marked as configuration files in the distro packages so that their modification does not cause verification failures (ex. rpm -qV)
Comment 1 Alexander Kurtakov CLA 2013-01-10 12:28:15 EST 
This would not happen as part of eclipse-build and dropins is still the better solution for linux distros. P2 is just unsuitable for our needs.