| Summary: | Prompt for license before contacting the server | ||
|---|---|---|---|
| Product: | [Tools] Oomph | Reporter: | Pascal Rapicault <pascal> |
| Component: | Setup | Assignee: | Eike Stepper <stepper> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | dennis.huebner, mike.milinkovich, stepper |
| Version: | 1.1.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Pascal Rapicault
It's maybe a dump question, but how should installer know, which licenses are included in a package w/o contacting the servers p2 repository? It is possible that there are different licenses in to accept, or at least different versions of EPL. (Note that I'm talking about this in the context of the simple installer being created to replace the EPP downloads, not the general oomph installer). At this point, the installer is able to present the set of EPP packages to install w/o contacting the p2 repos. Therefore, it should be able to obtain the licenses from the same source from where it obtained the list of packages. The (simple) installer has not been created (just) to replace the EPP downloads. That's one of its capabilities, but it has been created to simplify the installation of arbitrary Eclipse products that are registered in a reachable product catalog. We have discussed the option to ask users to accept at least the EPL (maybe the APL?) before they even get to the normal installer UI(s). Is there a document that describes all the goals of this new installer? No. The Foundation allows us to treat the two different SUA formats that exist in Luna SR2 and Mars (currently M6) as one. I'll add a one-time prompt for that at the beginning of an install process. That will not guarantee that no other licenses will need prompting later in the process, but should at least help with the simple "install an EPP package" cases. |