The aim is to get a tool to do the hard work of resolving package dependencies, so that the resulting jumpstart profile is nicely self-consistent. Doing this in the past has been very much a case of trial and error. No more!
I'll just show one screenshot here, of adding evolution on top of the reduced networking metacluster:
There's a lot more work than can be done here. The interface, while workable, is rather crude. I would like to get it to construct a reasonable jumpstart profile based on an installed system, and it would be nice to be able to feed it all my old profiles and get it to fix them up for me. And I'm sure there are many other ways it could be improved, or used in different ways.
So if you have any suggestions, give me a shout!
3 comments:
This is mint! Been looking for an easy way of getting my head round the packages and clusters in solaris.
Not quite as easy as say suse but pretty good effort.
Not to figure out the rest of the jumpstart profile config :)
This is stellar, Peter. Thank You!
As you're aware, having the ability to revise an existing profile (let alone generate the profile from a running system) would be tremendous.
-john
A very cool tool, peter!
Perhaps it would be worthwhile to implement (in Solview 0.5 :-) a "search tool", something like:
pkginfo | egrep
to quickly desume pkg names from one or
more keywords
-g.schmid
PS: a similar tool was recently posted
by g.brunette in opensolaris.org; however, it is just a ksh script suitable for CLI-only environments.
Post a Comment