[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cross-project-issues-dev] Re: [eclipse.org-planning-council] Re: EclipseCon memory stick and Ganymede M5
|
This is a great idea Pascal. Basically we get the best of both worlds
-- the Ganymede projects on an Update site AND the ability to install
the EPP packages. All that without any duplication.
Here I would suggest that we use p2 simply as an installer. In effect
p2 would "recreate" the exact same form that people would normally get
from the zip. The resultant configuration would not have p2 in it.
Once installed, users would use regular Update Manager to add more
features from the update site on the stick. This approach seems to be
a) quite straightforward to get in given the timeframe and b) is the
least disruptive to the cross-project team.
As for the installer, I'm assuming here that "installer.exe" is really
just eclipse.exe rebranded and that running it effectively just starts
up our p2 simple install UI. For that to work the user has to have Java
already on their path. As was observed in a previous thread, that
should be ok. If it is not, perhaps we can put Harmony on the stick :-)
One final point, if space becomes an issue then we can use pack200 but
that will require people to have a Java5 JRE as we currently do not have
an unpack implementation that can be shipped separately (nor does Harmony).
Summary, great direction, lets make this work!
Jeff
Pascal Rapicault wrote:
If space is the issue and what we are providing on the stick is not
supposed to be executable directly from it, then p2 could provide some help
bearing that you guys are ready to leave on the bleeding edge and my
teammates are agreeing that what I describe below is doable and is not a
distraction from our M6 goals.
short p2 introduction:
- p2 is capable of installing a complete product (exe, inis, etc.) from an
update site. There are some minor tweaks, but they are an implementation
details.
- p2 will provide a super simple installer. You click on the exe, it opens,
you say where you want to install, you click, you wait, done.
the stick:
Given p2, the stick becomes a p2 site that would contain all of ganymede.
In addition to this site, it contains an installer (based on the p2
installer) for each EPP package for all the platforms. When run, the
installer transparently installs the package from the site on the stick to
the user's disk.
So the stick shape could become:
Packages/
Java Developer/
win/
installer.exe
linux/
installer.exe
C++ Developer/
win/
installer.exe
...
Site/
plugins/
org.eclipse....
features/
org.eclipse....
site.xml
content.xml
Also if space was really an issue in that scenario we could even decide to
only put on the stick the pack.gz files.
Now what is really needed here:
- something to produce p2 data from an update site. This is already an M5
goal for p2 (next week). This would be used to p2-ize the Ganymede update
site
- provide a simple installer. This is already planned for M5 and we will
produce an installer for the SDK. Two weeks ago we have talked to the EPP
team about producing an installer for one of their package in the M5
timeframe. Obviously here we would have to produce installers for the 5
packages and we would have to improve the automation.
- p2 needs to be able to install on the mac (some problems with paths and
other details).
What do you think?
PaScaL
|------------>
| From: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Bjorn Freeman-Benson <bjorn.freeman-benson@xxxxxxxxxxx> |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|"eclipse.org-planning-council" <eclipse.org-planning-council@xxxxxxxxxxx>, Cross project issues <cross-project-issues-dev@xxxxxxxxxxx> |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|01/31/2008 04:59 PM |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|[eclipse.org-planning-council] Re: EclipseCon memory stick and Ganymede M5 |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
Here are the facts so far:
1. The following teams have said yes to a slightly compressed schedule
in order to fit the M5 EPP packages on the EclipseCon USB memory
stick:
1. TPTP
2. Modeling
3. DSDP/DD
4. Buckminster
5. Mylyn
6. DTP
2. The following teams have said no to a compressed schedule:
1. Webtools
3. Some projects (such as BIRT) are not included in EPP packages and
thus would not be included on the memory stick. Of course community
members and project leaders are welcome to create new packages (see
Ian's email) and be included.
4. Because we are buying so many memory sticks, our meeting planners
convinced the memory stick suppliers to accept Feb 22 (absolute drop
dead date) for us to supply the bits.
5. We can include approximately eight packages on the USB memory stick.
Currently there four packages (C, Java, JEE, RCP), thus we could
include two operating systems for each of those four. Win32 is our
number one download, so I think it's obvious that we would include at
least the Win32 packages.
Thus I propose:
The +3 projects agree to produce their M5 bits on the +2 date of Feb
18
The EPP builds will be on Feb 19
That gives us Feb 20 and 21 (Wednesday and Thursday) to test the
packages and decide if they are good enough to be "milestone quality"
Any objections?
- Bjorn
--
[end of message] _______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
