Matt Keenan wrote: > Sanjay Nadkarni wrote: >> On 07/13/09 12:17 PM, Jean McCormack wrote: >>> >>> There are several issues with respect to the addition of software >>> selection >>> in the installer that need to be addressed. >>> >>> 1) The user interface >>> >>> A user should have the option to install different software >>> collections (Desktop, AMP, HPC, ... etc.) >>> during installation that accompany the default installation. Each >>> collection should not include the 'kitchen sink' but be >>> representative of a useful and popular selection of software that >>> users typically use for that task. >>> >>> Frank has a screen shot of what he has come up with here: >>> http://xdesign.sfbay.sun.com/projects/solaris/subprojects/install/design/screensSlim08-11.html >>> >>> >>> If the number of collection choices is larger than about 6, we may >>> have to add a "Software" screen following the Welcome screen. >> Does it make sense to provide size for the collection. This might >> help the user. > > Just to be clear Package Manager does not define collections, it > defines a list > of categories (listed on left side of Package Manager UI), these > categories > are pre-defined and delivered as part of a file for the IPS package > itself. > > Are collections (as defined and talked about here), the same as > Categories ? > Or are they going to be defined by the install team itself, seems a > little > over kill to have to define them specifically, and would make sense of > both installer and package manager ui were in sync. Collections and Categories are different. The user cannot install a Category in IPS. What I would like is to add a new category in the Package Manager that would list the collections that the installer presents. This would provide a means for the installer to ask IPS for the list of collections and also make it easy for a user to install a collection, post system install, using the Package Manager. > > > > Concerning the rest of the discussions, I think the installer should > just provide a simple list of categories/collections, and if the user > wishes to customize these further, then they can either : > - Install collection and remove bits via package manager after install > - Install collection via Package Manager after initial install. > > Install UI experience should IMO be a simple/neat/quick experience as it > is now. This is what I have proposed.
Frank > > > I'm not sure providing a list of available REPO's is a good idea, users > should all install from a /release repo by default, they can use > package manager to define new authorities/repos where then can then > update/ > install from post initial install. Also providing a list of Repo's > available would require some network logic to ping these repo's to ensure > they are available. Would this need to be contained within the install > GUI or be provided via API the GUI ? > > cheers > > Matt > > >>> >>> >>> 2) What do we want to display in terms of data for the user with >>> regard to software collections? >>> >>> -Do we want to display the list of packages included in a software >>> collection to the users? -Do we want to provide the ability for >>> users to pick and choose >>> outside the collections? >>> -Marketing requirements seem to indicate we don't need to let users >>> pick individual packages(see above) >>> >>> Frank's response was the following which is reflected in the link >>> from #1 above: >>> The short answer is that I think we want to provide a short list >>> (<10?) of purpose focused "collections" without listing specific >>> packages, though we might provide a short description next to a >>> collection that lists the major "applications" in that collection. >>> I believe that the collections should contain a reasonably complete >>> set of packages for that function, but selecting all collections >>> would not necessarily load all packages in the repo. The package >>> manager could be used to fine tune the package set after >>> installation. >>> >>> 3) How can we maintain the list of packages now, since IPS does not >>> currently provide an API for querying for the info.classification tag? >>> >>> Evan did some research on this, the summary of which follows: >>> "The current Package Manager is maintaining it's own set of >>> "collections" or groupings and that using the currently available >>> tools we would have to do the same, using something like the .p5i >>> files to define these. >>> >>> Going forward the IPS client API will be enhanced to allow us to use >>> the info.classification tag and query IPS for this information for >>> dynamically building up these collections or groupings. " >>> >>> >> I am unclear if the interfaces provide access to the Package >> Manager's collection or is it something that is provided by IPS ? >> >> >>> 4) Method of installation >>> >>> >>> I had a discussion with Sarah about our current methods of >>> installations: >>> 1) Everything is installed from media (current liveCD). Fast but >>> not easily customizable. >>> 2) Everything is installed from IPS repo (current AI). >>> Customizable but slow. >>> >>> >>> This project proposes to implement the following: >>> 1) LiveCD contents are installed from media. >>> 2) Selected package collections are available to customize the >>> installation via IPS. >>> >>> Phase 1 of the project will install the software collections from >>> the network >>> Phase 2 of the project will allow installing the software >>> collections from the IPS repo on a disk. >>> >>> >>> >>> _______________________________________________ >>> caiman-discuss mailing list >>> caiman-discuss at opensolaris.org >>> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >> >> _______________________________________________ >> caiman-discuss mailing list >> caiman-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss > > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
