| Summary: | Profile preferences not accessible in shared install | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | John Arthorne <john.arthorne> |
| Component: | p2 | Assignee: | P2 Inbox <equinox.p2-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | contact, irbull, simon_kaegi |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
| Whiteboard: | |||
|
Description
John Arthorne
To be celar, this is not new behavior. The preferences have never cascaded. Ok, good to know. I hadn't decided in my mind yet if this was a bad thing or not. The administrator might want to use different sites to configure the system, and not have these sites bleed through to regular users... To be honest I haven't decided one way or the other either. I don't really want to close so instead I'll make it an enhancement request for now. *** Bug 234927 has been marked as a duplicate of this bug. *** I'm not going to pretend to know all the implications, but having the repositories available in cascaded profiles would prevent me having to tell people who use our RPMs how to add the release train repos to their list of repositories. *** This bug has been marked as a duplicate of bug 249133 *** |