> MC wrote: > >> the SUNW is part of the package name, it's also > what the pkg commands expect[s] > >> > > > > But does that matter for a graphical app like this? > I haven't used it yet, but almost every package > having SUNW on the front in the GUI doesn't help me > at all, I'm pretty sure. > > > > end to agree that it doesn't matter in a GUI tool. > Maybe to help is > nstead of putting "Installed Solaris Packages" in a > tab, you could just > put SUNW there and for Blastwave packages tab just > put CSW or maybe add > a button to toggle the information back and forth of > just have a > preference feature to display it a particular way.
There should be a configurable list of package prefixes with descriptions then, and optional grouping, too. Descriptions might look like SUNW Supplier: Sun Microsystems VRTS Supplier: Veritas (now Symantec) CSW Supplier: blastwave.org etc. To the extent that they were downloadable independently, the top-level URL from which updates could be found might be something one would want to store as well, along with who knows what other information. I think I'd want to fetch dependency information from the repositories though (preferably without having to actually download a package to find out its dependencies, so I could get an assessment of what would be updated, the total size of downloads, other packages that would be affected by updated dependencies (and if there were some for which corresponding updates were not available). To do that without downloading packages would require the repositories to have the necessary information available, in stable, documented locations and formats. Trends being what they are, I suppose there would be a hierarchy of XML configuration files... This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
