>>> 4) Here's a new option... The database could be changed to >>> distinguish, say, http links which go to webpages requiring >>> navigation, vs http links which go to downloadable files. This way, >>> the DDU can know which links it can download from, and which ones it >>> can only display in a "manually download" message. >>> >>> Right now the database has categories of: >>> S - solaris driver (names in these entries are pkg(5) names - only >>> this category can be installed by the DDU currently AFAIK) >>> T - third party driver >>> O - OpenSolaris driver (from opensolaris projects, webpages given, >>> not package names) >>> >>> I suggest splitting the T and O categories into separate ones for >>> links pointing to installable files, or not. All S category items >>> are installable via pkg(1). >>> >> >> Another option that I think is possibly better is to enhance the >> database to allow specification of both a direct link and an >> informational link. The latter is appropriate for interactive uses, >> but not automatic ones. > OK. I like this idea, but it may be a lot of work. I'll propose it to > the DDU team; if they are too busy, then option 4 can be a fallback. >
I'd think the up-front work required is roughly equivalent; the existing links can be categorized as one or the other in the new format and later updates can provide the others, if they're available. Dave
