It seems like there are better ways of determining this information, instead of looking through all of the manifests, and examining the size attributes.
The pkg client doesn't know how large an install will be until it has evaluated an imageplan. Once the evaluation has completed, we actually have the number of packages and bytes available. It seems like it would make more sense to plug at the end of imageplan.evaluate, than it would to do really slow and painful things. You could always prompt the user to abort between the evaluate and the download phases. -j On Thu, Sep 25, 2008 at 03:23:50PM -0700, Brock Pytlik wrote: > John Rice wrote: > >>> Its the size we want :( Tends to be more relevant for updates for users. > >>> > >> So how were you getting size quickly in the past? > >> > > Slowly :) as part of the description. The UM GUI just makes it more > > obvious, the user tends to want to know how big an upgrade is before > > hitting install. > > > Ok, since this isn't a regression, I'm going to say it probably won't > make it for november, unless someone would like to step up and add it > into the API themselves. My feeling is that just getting what we have > integrated well with the GUI and the CLI (both of which are ever moving > targets) will be hard enough without adding more features to the problem. > > Brock > >>> [snip] > >>> > > _______________________________________________ > pkg-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/pkg-discuss _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
