Brian Cameron writes: > Perhaps you misunderstand how codeina works, or I misunderstand > something. The codeina application autodetects when a user tries to > play a file that can't be played due to a lack of a codec. If Fluendo > offers a codec for sale that enables playing that format, it pops up > a window. The window steps the user through purchasing the plugin > (via a mozembed plugin accessing their webstore), then after purchase > it downloads the package and installs the plugins for you.
I think there might be some simple ways to do this. One would be to have the codeina install process itself save a file somewhere on the system (under /var might be good) indicating exactly what kind of package was used to install codeina itself, and where it was installed from. Each distribution format of codeina can install a different file indicating how and where to get more. You then use this at run time to determine how to get more packages. The assumption is that the mechanism used to install codeina is the same as the common one that the user wants for all packages, and that you can have slightly different data in each package format you distribute, generated as part of the packaging process. I think the worst way to solve this problem would be to condition the logic based on the "platform." There's no obvious or reliable technical definition of "platform" (it's more of a marketing issue), nor does there appear to be a way to tie "platform" into anything about preferred installation method. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-discuss mailing list [email protected]
