Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] [prov] EclipseCon installers


Right. As I said - "Unless I am missing something..."

Can't help but anticipate the brave new world. We'll get there someday.

        - Dave



Re: [equinox-dev] [prov] EclipseCon installers

John Arthorne to: Equinox development mailing list
02/04/2008 07:37 PM

Sent by: equinox-dev-bounces@xxxxxxxxxxx

Please respond to Equinox development mailing list <equinox-dev@xxxxxxxxxxx>








I'm not sure I follow... are you suggesting we install the installer using p2?  Currently the installer is just a plain zipped Equinox/SWT application.




David R Stevenson <dstevens@xxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

02/04/2008 07:05 PM

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

To
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
cc
Subject
Re: [equinox-dev] [prov] EclipseCon installers








Unless I am missing something, we should be able to bundle all the launchers as IUs in the same package, each with the appropriate filters for os and arch. Then the correct launcher will be selected at install time. That is something difficult to do with a zip, but should be simple in p2.


      - Dave


Re: [equinox-dev] [prov] EclipseCon installers



John Arthorne to: Equinox development mailing list
02/04/2008 10:33 AM



Sent by: equinox-dev-bounces@xxxxxxxxxxx



Please respond to Equinox development mailing list <equinox-dev@xxxxxxxxxxx>










I believe we need a different installer per platform (os/ws/arch), since they will have different launchers, unless there is some known way to bundle a standalone RCP application that will run on any platform.  As for EPP packages, the installer works by reading an install description file that specifies what to install, where to get the bits from, etc.  The description file is passed to the installer as a system property on the command line, or in the installer.ini file. Since each EPP package will just be represented by a different install description file, one could imagine a single installer with a series of scripts/batch files that pass in a different property for the description file.  On the other hand, the installer is currently ~4MB (of which 2MB is SWT), so for simplicity having a separate installer per EPP per platform could also work.


John

Jeff McAffer <jeff@xxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

02/04/2008 01:13 PM

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>


To
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
cc
Subject
[equinox-dev] [prov] EclipseCon installers











I forgot to ask during the call.  Can we have one installer per EPP
package?  That is, one installer that would work for multiple platforms
or do we have to have one installer for per EPP per platform?

Jeff
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev

_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev


Back to the top