Darren: >> I will need to check with Fluendo if purchasing an x86 plugin allows >> you to >> migrate to a Sparc plugin (or a plugin for a different distro for that >> matter) in the future, or if users need to buy a new set of plugins when >> switching from x86 to Sparc or vice versa. I will respond when I get an >> answer.
Currently Fluendo requires you to purchase a separate set of plugins per architecture. However Julien Moutte, the owner of Fluendo told me that they are working on a new version of the server side of the store that will allow anyone to download for the platform they want and they can change on the fly. So this is a planned future enhancement. > Regardless of the licensing issue I REALLY REALLY don't want to need to > keep going back to the Fluendo server just because my current system as > switch from x86 to SPARC or vice versa - in fact there maybe situations > where I can't do that because I don't have the network connectivity to > Fluendo at that tiem. > > The real solution here is to switch the install location to > .gnome/plugins/`uname -p`. If the plugins have different filenames or are intalled to different subdirectories of $HOME/.gstreamer-0.10/plugins (as you suggest above with "uname -p"), then GStreamer does support the same $HOME directory having plugins for different architectures. However, codeina unfortunately does not yet take advantage of this feature. Since their x86 and Sparc plugins have the same name, you can only install one of them at a time (unless a user were to rename them or install them to arch-specific subdirs by hand). In talking with the codeina developers, they had not considered this use case before. I filed a bug against codeina about this issue, so it can get addressed. https://core.fluendo.com/gstreamer/trac/ticket/169 Brian
