Frank Ludolph wrote: > Matt Keenan wrote: >> 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.
A group package would be preferable to a category. See my response to the initial post of this thread for why. >> 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. This would be my hope as well. Most of the new OS installers I have seen have chosen to remove customisation over the years in favour of simplicity and accessibility. pkg(1) and packagemanager are the right tools to use to customise what is installed on the system *after* the base system image has been installed. Cheers, -- Shawn Walker
