> > That makes 1,819 reasons why we need a new method > for package > > installation for [Open]Solaris. > > yea verily. > Personally I think that the SVR4 package format is > well established, > rusted and reliable. I am doing more than just > thinking out loud on > this also. I am really looking at a prototype here > in the Blastwave > basement. That is why I happened to have the package > list in front of me > and I have been creating categories for software. > Those manpage type > ackages all fall under a category called "docs". So > in one fell swoop a > user can issue a simple command and have all docs > arrive, get unpacked > and installed. So simple it is just stupid to not do > it. All commands > and utilities fall under "tools and utilities" and to > some extent this is > just me following the single UNIX spec and ticking > off things from a > shopping list. > > anyways ... I am tinkering with it.
I would think that the hard part is grouping the packages helpfully, along with doing so in a manner that avoids dependencies when possible (all packages in a group only dependent on core packages or on packages within that group, in the latter case with the packages in proper order) and handles inter-group dependencies when they can't be avoided. I'm pathetic in perl, but I suppose perl/tk would be great for that; probably lots of cool XML parser modules available, so that one could design a nice format to describe groups, the packages within them, intra- and inter-group dependencies, etc. One could probably do both a GUI and a curses-like interface from a script even. This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list [email protected]
