Bugzilla – Full Text Bug Listing
| Summary: | Available Software work with should default to all available sites | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Andrew Overholt <overholt> |
| Component: | p2 | Assignee: | P2 Inbox <equinox.p2-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | susan |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 267852 | ||
| Bug Blocks: | |||
|
Description
Andrew Overholt
I see at [1] that this is desired behaviour. [1] http://wiki.eclipse.org/Equinox/p2/UI_Manual_Tests#Areas_of_Emphasis Is there supposed to be some sort of background loading of repositories? If so, I don't see this working. (In reply to comment #2) > Is there supposed to be some sort of background loading of repositories? If > so, I don't see this working. There is a problem with composite repos right now that is causing this. As for the behavior, I'm interested in your comments regarding the new workflow. Did you want "All Available Sites" so that you could test, or because you are used to it, or because you really want it to work that way? And do you see this change as confusing for your users? We're trying to determine if a preference (even if it's hidden from users) should drive this behavior. (In reply to comment #3) > (In reply to comment #2) > > Is there supposed to be some sort of background loading of repositories? If > > so, I don't see this working. > > There is a problem with composite repos right now that is causing this. Okay. > As for the behavior, I'm interested in your comments regarding the new > workflow. Did you want "All Available Sites" so that you could test, or > because you are used to it, or because you really want it to work that way? > And do you see this change as confusing for your users? It was confusing to me. I expect it would be confusing to others who are used to enabled repositories always being enabled. Not seeing any available (or installed) software made me think something was wrong. > It was confusing to me. I expect it would be confusing to others who are used > to enabled repositories always being enabled. Not seeing any available (or > installed) software made me think something was wrong. > The confusion problem is documented in bug 258105, with the intention being to put something in the list that says "there are no sites selected blah blah blah." Kind of like the syncrhonize view in CVS when it's empty. So I could close this bug as a duplicate of that one. However, if you think we need to consider allowing more configuration of the default by products or users, this bug should stay open. (In reply to comment #5) > > It was confusing to me. I expect it would be confusing to others who are used > > to enabled repositories always being enabled. Not seeing any available (or > > installed) software made me think something was wrong. > > > > The confusion problem is documented in bug 258105, with the intention being to > put something in the list that says "there are no sites selected blah blah > blah." Kind of like the syncrhonize view in CVS when it's empty. > > So I could close this bug as a duplicate of that one. You can close it assuming the behaviour is expected. Sorry about the dupe on the confusion. > You can close it assuming the behaviour is expected. Sorry about the dupe on > the confusion. Gosh, Andrew, why haven't you memorized all the p2 UI bugs? ;-) *** This bug has been marked as a duplicate of bug 258105 *** |