I am currently working with some engineers at Fluendo to help them provide their media plugins for OpenSolaris and also to help make the codeina program work on both Solaris and OpenSolaris. I have a few questions I am hoping you can help with.
The codeina client program sets 4 variables to identify what system its running on. These are: OS, ARCH, DISTRO and DISTRO_VERSION. These don't need to all be set to unqiue values for each Solaris or OpenSolaris release, but instead only need to identify if Fluendo needs to ship different packages for a given system. So, in other words, DISTRO_VERSION probably only needs to be incremented if the packaging system or binary compatibly changes between versions. We were thinking it would make sense to set OS to Python's os.uname() value. It returns 'SunOS' as system name and 'i86pc' or 'sun4u' for Intel and Sparc architectures. This seems to be the same on both Solaris and OpenSolaris. So we were thinking of using these for the OS and ARCH values. Is this reasonable for both Solaris and OpenSolaris moving forwards, or should we be using some other more recommended interface? We could set DISTRO="generic" and DISTRO_VERSION to "any", which are codeina's default values if it isn't necessary to differentiate. However, since Solaris and OpenSolaris have different packaging systems I think we might need to set DISTRO to "solaris" or "opensolaris". Is this correct? Or is it possible and advisable for Fluendo to just provide a single set of Solaris packages and install them in both Solaris and OpenSolaris? I know Fluendo would prefer this if possible, and avoid having to provide their code in different packaging system formats. Assuming that isn't possible, and they need to provide different styles of packages for Solaris versus OpenSolaris, then what is the recommended interface to use to identify whether the codeina client is running on Solaris versus OpenSolaris? Any advise would be appreciated. It would be good to get the Fluendo codeina server/client set up properly now and avoid problems in the future. Then users will be able to download useful media and popular codecs from the Fluendo webstore via codeina easily. Note that Fluendo hopes to have MPEG-2 and MPEG-4 decoder codecs available for sale for Solaris by the end of the year. So that's exciting news. Thanks, Brian _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
