Community
Participate
Working Groups
In order for the Update Manager to provide useful numbers in the Required space display, the features to be installed must specify the install-size attribute within all their <plugin> tags in the feature manifests. It'd be very nice if all of the Callisto projects did this - to provide accurate information while using the Update Manager to install the Callisto release. While we're at it, it'd probably be a good idea to specifiy the download-size attribute as well.
Moving to Callisto.
[from cross-project-issues-dev, Callisto 3.2RC4a] Issue 9: Required space was unknown for all features. What's the use of printing required and available space if it's always going to be unknown? I think the required space should be automatically figured out by the build process.
*** Bug 148679 has been marked as a duplicate of this bug. ***
Any chance of a last-minute push from the powers that be to get this done before the Callisto release date?
From the perspective of the platform/jdt/pde/equinox project, there isn't currently tooling in pde build to support this. We would have to add this support to our builds to determine the size of the various plugins and then crack open the jarred features to update them with this information. At this time of the Callisto endgame this is not possible for our project and is something we will investigate for Eclipse 3.3.
Yeah, I was hoping for each project updating their features manually. The values don't have to be completely accurate to a byte to be useful - so they don't really have to be tracked build to build. A rough estimate done manually (I'd be satisfied with numbers +- 50K) was what I was looking for in Callisto.
No, we will have to include this as part of our build process. Speaking for the platform project, it's not scaleable as a manual step.
It'd be great to have this as part of the build process. I'd also be great to have this done for Callisto. Right now, I'm more interested in solving the second goal, since the first can't happen in time.
I'm sure everybody would appreciate if you could fix the pb in the callisto timeframe.
While nice to have, my own thought is its too late. Callisto as a whole is under the same rules as the individual projects. Only blockers and stop ship problems will be addressed these last few days. And, honestly Jeff, " ... updating their features manually ..." you should know that would never go smoothly :)
I know, I know. But a boy can dream...
For my update site at http://download.eclipse.org/dsdp/tm/updates, I have manually defined download-size and install-size for all plugins. Doing so, I noticed two issues: 1. Although sizes are defined, Update Manager shows feature sizes as "unknown" when the update site has a digest.zip. See bug 163406. 2. For SDK and source features, there is no easy way to specify the install and download sizes for the generated sources. Unless a static copy of feature.xml is used, which seems not a good idea. --> There really is a REQUIREMENT to add a capability to PDE build that computes download and install sizes automatically, at least for generated features.
Callisto is past, so is Europa. I've added this to the Ganymede requirements but am closing as INVALID because the bug says "Callisto".
