From bc99092@sac.sfbay.sun.com Thu Nov 13 14:43:42 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mADMhfnS003758 for ; Thu, 13 Nov 2008 14:43:42 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id mADMhaN7018030; Fri, 14 Nov 2008 06:43:40 +0800 (SGT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KAA00A03N4PTQ00@brm-avmta-1.central.sun.com>; Thu, 13 Nov 2008 15:43:37 -0700 (MST) Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KAA00M64N4O3E90@brm-avmta-1.central.sun.com>; Thu, 13 Nov 2008 15:43:36 -0700 (MST) Received: from sac.sfbay.sun.com (new-sac.SFBay.Sun.COM [129.146.175.65]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id mADMharA014939; Thu, 13 Nov 2008 14:43:36 -0800 (PST) Received: from sac.sfbay.sun.com (localhost [127.0.0.1]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mADMhYin003706; Thu, 13 Nov 2008 14:43:34 -0800 (PST) Received: (from bc99092@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id mADMhYrE003702; Thu, 13 Nov 2008 14:43:34 -0800 (PST) Date: Thu, 13 Nov 2008 14:43:34 -0800 (PST) From: Brian Cameron Subject: codeina [LSARC/2008/709 FastTrack timeout 11/25/2008] To: LSARC-ext@sun.com Cc: desktop-discuss@opensolaris.org Message-id: <200811132243.mADMhYrE003702@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 10458 Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2008 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: codeina 1.2. Name of Document Author/Supplier: Author: Brian Cameron 1.3 Date of This Document: 13 November, 2008 4. Technical Description 1. Introduction 1.1. Project/Component Working Name: codina 1.2. Name of Document Author/Supplier: Brian Cameron 1.3. Date of This Document: 11/06/2008 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: Solaris PAC 1.4.2. The ARC(s) you expect to review your project: LSARC 1.4.3. The Director/VP who is "Sponsoring" this project: Robert O'Dea 1.4.4. The name of your business unit: Software - OPG 1.5. Email Aliases: 1.5.1. Responsible Manager: leo.binchy@sun.com 1.5.2. Responsible Engineer: brian.cameron@sun.com 1.5.3 Marketing Manager: dan.robert@sun.com 1.5.4. Interest List: desktop-discuss@opensolaris.org 2. Project Summary 2.1. Project Description: codeina is an Fleundo application written in Python which simplifies the process for users to discover and install GStreamer multimedia plugins on their system. 4. Technical Description: 4.1. Details: codeina is a client application from the Fluendo company which steps the user through the process of buying and installing GStreamer multimedia codec plugins. It uses an embedded browser in the application to talk to a web server. By default codeina on Solaris only supports connecting to the Fluendo server. Once connected, the user can navigate through web pages to select plugins to download and install. The codeina application can be run in two ways: - As a standalone program. In this case, a full list of available plugins are presented to the user. The user can select a plugin and is stepped through the process of downloading and installing the plugin. - GStreamer supports the GST_INSTALL_PLUGINS_HELPER environment variable. If a user tries to play a media format that is not supported by available installed GStreamer plugins, then it will run the program specified in this environment variable. By ensuring that the user's session has this environment variable set to "/usr/bin/codeina", then the codeina program will be launched. GStreamer itself (in the gst-plugins-base module) can be configured to use a default value when the environment variable is not set via the gst-plugins-base configure --with-install-plugins-helper option. This method would be used to ensure codeina is used when integrating codeina into Solaris. When codeina is launched via these GStreamer mechanisms, codeina checks a list of configured servers to see if any server has a plugin available to play this media type. If not, then codeina just exits and allows the application to inform the user the media type cannot be played. If a plugin is found, then codeina steps through the process of downloading and installing the plugin. If more than one plugin is found, the user can select which plugin they wish to download install. Some plugins may be free. In this case, the user can simply download and install the plugin immediately. Other plugins may be available only for a fee. This is typical with plugins that require a license fee to use (such as WindowsMedia, MP3, MPEG-2, or MPEG-4). In this situation, codeina presents the user with a webstore defined by the server where the user can pay for the plugin (perhaps by credit card or PayPal). Codina uses PyOpenSSL to support HTTPS secure web interactions for navigating websites that require such billing. In addition, codeina provides an autostart feature so that codeina is always run with the user session with the "-u --sleep 5" arguments. This causes codeina to check with the server periodically to see if there are any updates to any plugins previously downloaded via codina. If so, then the user is stepped through the process of downloading and installing the updates. By default, when codeina installs a plugin, it installs it to the $HOME/.gstreamer/plugins directory so that the user immediately is able to use the plugin. The codeina application also provide hooks so that a distro can provide additional plugins from other web resources. This is managed via codeina's "providers" files. By providing a "providers" file, a distro can make available either free plugins or plugins that are for sale. The providers file has hooks so that a distro can specify their own installation plugin which will step the user through a specified webstore purchasing process for billing. Though, this obviously requires that the distro set up the webstore service and write a installation plugin for codeina. codeina keeps track of each platform internally by keeping track of the following variables which are set as follows on Solaris: OS_NAME = "SunOS" ARCH_NAME = "sparc" or "i386" DISTRO_NAME = "solaris" DISTRO_VERSION = "any" These values are used in handshaking between the client and server in order to identify which plugins are available for a given client. If, for example, Sun were to set up a providers file which pointed to a Sun specific server, then the server would need to be configured to identify the Sun client using these parameters. Likewise codeina provides hooks so that a distro can customize how plugins are installed if desired. Although some distros (such as Red Hat and Mandriva Linux) have made us of such integration hooks (such as providers files), the interfaces are not documented. Fluendo plans to make these interfaces more public in the future so that it is easier for distros to integrate with codeina. In the meantime they should be considered Volatile interfaces. 4.2. Interfaces: Exported Interfaces Stability Comments --------------------------------------- ----------- ---------------- SUNWcodeina Uncommitted Package name. SUNWcodeina-root Uncommitted Package name. /usr/bin/codeina Volatile Script for starting codeina /usr/bin/codeina.bin Volatile The codeina application /usr/lib/python/2.4/vendor-packages/codeina Project Python Private implementation of codina /usr/share/applications/codeina.desktop Volatile Desktop file /usr/share/autostart/codeina-update-kde.desktop for when KDE is the desktop being used. /usr/share/codeina Project Private Private directory for icons and logos /etc/codeina/providers Volatile Providers directory /etc/codeina/providers/fluendo.xml Volatile Fluendo providers file /etc/xdg/autostart/codeina-update.desktop $XDG_CONFIG_HOME/share/codeina Volatile User config $HOME/.gstreamer-0.10/plugins Volatile GStreamer user plugin directory Imported Interfaces Stability Comments --------------- --------------- ----------------------- SUNWpython-libs Unstable LSARC 2005/506 Python External PSARC/2005/532 Python Evolving Migration from /usr/sfw to /usr and upgrade to v2.4.x GStreamer Volatile LSARC 2006/202 Python XDG Uncommitted PSARC 2008/104 SUNWgst-python Uncommitted PSARC 2008/105 python-notify Uncommitted PSARC 2008/419 PyYAML Uncommitted PSARC 2008/676 PyOpenSSL Uncommitted 4.3. Doc Impact: Man page is needed. 4.4. Packaging & Delivery: SUNWcodeina, SUNWcodeina-root - packages for codeina. 4.5. Dependencies: None. 4.6. L10N Impact: The Desktop team and the G11N are working together to evaluate and provide I18N/L10N support. 4.7. Security Impact: None. 5. Reference Documents: The codeina website: https://core.fluendo.com/gstreamer/trac/wiki/codeina Other information about codeina: http://fedoraproject.org/wiki/Multimedia/Codeina http://fedoraproject.org/wiki/Releases/FeatureCodecBuddy 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: Desktop 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From John.Fischer@sun.com Thu Nov 13 15:09:59 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mADN9wAP006493 for ; Thu, 13 Nov 2008 15:09:59 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mADN9rTa001232 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Thu, 13 Nov 2008 15:09:58 -0800 (PST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KAA0000DOCGUQ00@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.Com); Thu, 13 Nov 2008 15:09:52 -0800 (PST) Received: from brmea-mail-4.sun.com ([192.18.98.36]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KAA00GSVOCF3XB0@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.Com); Thu, 13 Nov 2008 15:09:51 -0800 (PST) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mADN9pKk016052 for ; Thu, 13 Nov 2008 23:09:51 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KAA00H01O3RHW00@mail-amer.sun.com> (original mail from John.Fischer@Sun.COM) for LSARC-ext@Sun.Com (ORCPT LSARC-ext@Sun.Com); Thu, 13 Nov 2008 16:09:51 -0700 (MST) Received: from 129.145.154.66 ([129.145.154.66]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KAA00AW5OCERBA0@mail-amer.sun.com>; Thu, 13 Nov 2008 16:09:51 -0700 (MST) Date: Thu, 13 Nov 2008 15:09:49 -0800 From: John Fischer Subject: Re: codeina [LSARC/2008/709 FastTrack timeout 11/25/2008] In-reply-to: <200811132243.mADMhYrE003702@sac.sfbay.sun.com> Sender: John.Fischer@sun.com To: Brian Cameron Cc: LSARC-ext@sun.com, desktop-discuss@opensolaris.org Reply-to: John.Fischer@sun.com Message-id: <1226617789.49887.302.camel@sr1-umpk-16> MIME-version: 1.0 X-Mailer: Ximian Evolution 1.4.6.301 Content-type: text/plain; charset=ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200811132243.mADMhYrE003702@sac.sfbay.sun.com> Status: RO Content-Length: 11690 Brian, A couple of questions.... 1. Does this project set a precedent in that we now expect projects to provide KDE hooks? If so then what are the said hooks? 2. How does this project deal with a user who switches between SPARC and x86? How does this project deal with a user who switches their Sun Ray server via utswitch? What if the server was SPARC and is now x86? Are the implications of this that the user would have to purchase a new plugin? Would the difference in system architecture cause the application to fail? Would the difference in system architecture cause the mechanism to overwrite the previous version? Thanks, John On Thu, 2008-11-13 at 14:43, Brian Cameron wrote: > Template Version: @(#)sac_nextcase %I% %G% SMI > This information is Copyright 2008 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > codeina > 1.2. Name of Document Author/Supplier: > Author: Brian Cameron > 1.3 Date of This Document: > 13 November, 2008 > 4. Technical Description > > 1. Introduction > > 1.1. Project/Component Working Name: > > codina > > 1.2. Name of Document Author/Supplier: > > Brian Cameron > > 1.3. Date of This Document: > > 11/06/2008 > > 1.4. Name of Major Document Customer(s)/Consumer(s): > 1.4.1. The PAC or CPT you expect to review your project: > > Solaris PAC > > 1.4.2. The ARC(s) you expect to review your project: > > LSARC > > 1.4.3. The Director/VP who is "Sponsoring" this project: > > Robert O'Dea > > 1.4.4. The name of your business unit: > > Software - OPG > > 1.5. Email Aliases: > 1.5.1. Responsible Manager: > > leo.binchy@sun.com > > 1.5.2. Responsible Engineer: > > brian.cameron@sun.com > > 1.5.3 Marketing Manager: > > dan.robert@sun.com > > 1.5.4. Interest List: > > desktop-discuss@opensolaris.org > > 2. Project Summary > 2.1. Project Description: > > codeina is an Fleundo application written in Python which simplifies > the process for users to discover and install GStreamer multimedia > plugins on their system. > > 4. Technical Description: > 4.1. Details: > > codeina is a client application from the Fluendo company which steps > the user through the process of buying and installing GStreamer > multimedia codec plugins. It uses an embedded browser in the > application to talk to a web server. By default codeina on Solaris > only supports connecting to the Fluendo server. Once connected, the > user can navigate through web pages to select plugins to download and > install. > > The codeina application can be run in two ways: > > - As a standalone program. In this case, a full list of available > plugins are presented to the user. The user can select a plugin > and is stepped through the process of downloading and installing > the plugin. > > - GStreamer supports the GST_INSTALL_PLUGINS_HELPER environment > variable. If a user tries to play a media format that is not > supported by available installed GStreamer plugins, then it will run > the program specified in this environment variable. By ensuring that > the user's session has this environment variable set to > "/usr/bin/codeina", then the codeina program will be launched. > > GStreamer itself (in the gst-plugins-base module) can be configured > to use a default value when the environment variable is not set via > the gst-plugins-base configure --with-install-plugins-helper option. > This method would be used to ensure codeina is used when integrating > codeina into Solaris. > > When codeina is launched via these GStreamer mechanisms, codeina > checks a list of configured servers to see if any server has a plugin > available to play this media type. If not, then codeina just exits > and allows the application to inform the user the media type cannot > be played. > > If a plugin is found, then codeina steps through the process of > downloading and installing the plugin. If more than one plugin is > found, the user can select which plugin they wish to download > install. > > Some plugins may be free. In this case, the user can simply download > and install the plugin immediately. Other plugins may be available > only for a fee. This is typical with plugins that require a license > fee to use (such as WindowsMedia, MP3, MPEG-2, or MPEG-4). In this > situation, codeina presents the user with a webstore defined by the > server where the user can pay for the plugin (perhaps by credit card or > PayPal). Codina uses PyOpenSSL to support HTTPS secure web > interactions for navigating websites that require such billing. > > In addition, codeina provides an autostart feature so that codeina is > always run with the user session with the "-u --sleep 5" arguments. > This causes codeina to check with the server periodically to see if > there are any updates to any plugins previously downloaded via codina. > If so, then the user is stepped through the process of downloading and > installing the updates. > > By default, when codeina installs a plugin, it installs it to the > $HOME/.gstreamer/plugins directory so that the user immediately is able > to use the plugin. > > The codeina application also provide hooks so that a distro can provide > additional plugins from other web resources. This is managed via > codeina's "providers" files. By providing a "providers" file, a > distro can make available either free plugins or plugins that are for > sale. The providers file has hooks so that a distro can specify their > own installation plugin which will step the user through a specified > webstore purchasing process for billing. Though, this obviously > requires that the distro set up the webstore service and write a > installation plugin for codeina. > > codeina keeps track of each platform internally by keeping track of the > following variables which are set as follows on Solaris: > > OS_NAME = "SunOS" > ARCH_NAME = "sparc" or "i386" > DISTRO_NAME = "solaris" > DISTRO_VERSION = "any" > > These values are used in handshaking between the client and server in > order to identify which plugins are available for a given client. If, > for example, Sun were to set up a providers file which pointed to a > Sun specific server, then the server would need to be configured to > identify the Sun client using these parameters. > > Likewise codeina provides hooks so that a distro can customize how > plugins are installed if desired. > > Although some distros (such as Red Hat and Mandriva Linux) have made > us of such integration hooks (such as providers files), the interfaces > are not documented. Fluendo plans to make these interfaces more public > in the future so that it is easier for distros to integrate with > codeina. In the meantime they should be considered Volatile interfaces. > > 4.2. Interfaces: > > Exported Interfaces Stability Comments > --------------------------------------- ----------- ---------------- > SUNWcodeina Uncommitted Package name. > SUNWcodeina-root Uncommitted Package name. > /usr/bin/codeina Volatile Script for > starting > codeina > /usr/bin/codeina.bin Volatile The codeina > application > /usr/lib/python/2.4/vendor-packages/codeina Project Python > Private implementation > of codina > /usr/share/applications/codeina.desktop Volatile Desktop file > /usr/share/autostart/codeina-update-kde.desktop for when KDE is > the desktop > being used. > /usr/share/codeina Project Private > Private directory for > icons and logos > /etc/codeina/providers Volatile Providers > directory > /etc/codeina/providers/fluendo.xml Volatile Fluendo > providers file > /etc/xdg/autostart/codeina-update.desktop > $XDG_CONFIG_HOME/share/codeina Volatile User config > $HOME/.gstreamer-0.10/plugins Volatile GStreamer user > plugin > directory > > Imported Interfaces Stability Comments > --------------- --------------- ----------------------- > SUNWpython-libs Unstable LSARC 2005/506 > Python External PSARC/2005/532 Python > Evolving Migration from /usr/sfw > to /usr and upgrade to v2.4.x > GStreamer Volatile LSARC 2006/202 > Python XDG Uncommitted PSARC 2008/104 > SUNWgst-python Uncommitted PSARC 2008/105 > python-notify Uncommitted PSARC 2008/419 > PyYAML Uncommitted PSARC 2008/676 > PyOpenSSL Uncommitted > > 4.3. Doc Impact: > > Man page is needed. > > 4.4. Packaging & Delivery: > > SUNWcodeina, SUNWcodeina-root - packages for codeina. > > 4.5. Dependencies: > > None. > > 4.6. L10N Impact: > > The Desktop team and the G11N are working together to evaluate and > provide I18N/L10N support. > > 4.7. Security Impact: > > None. > > 5. Reference Documents: > > The codeina website: > https://core.fluendo.com/gstreamer/trac/wiki/codeina > > Other information about codeina: > http://fedoraproject.org/wiki/Multimedia/Codeina > http://fedoraproject.org/wiki/Releases/FeatureCodecBuddy > > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > Desktop > 6.5. ARC review type: FastTrack > 6.6. ARC Exposure: open > From Brian.Cameron@sun.com Thu Nov 13 15:25:38 2008 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mADNPcdK007323 for ; Thu, 13 Nov 2008 15:25:38 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mADNPaD8029702 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Thu, 13 Nov 2008 15:25:38 -0800 (PST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KAA00D07P2OYI00@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.Com); Thu, 13 Nov 2008 16:25:36 -0700 (MST) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KAA00MJ7P2N2UC0@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.Com); Thu, 13 Nov 2008 16:25:35 -0700 (MST) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mADNPZMl004345 for ; Thu, 13 Nov 2008 23:25:35 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KAA00801O3JWK00@mail-amer.sun.com> (original mail from Brian.Cameron@Sun.COM) for LSARC-ext@Sun.Com (ORCPT LSARC-ext@Sun.Com); Thu, 13 Nov 2008 16:25:35 -0700 (MST) Received: from [10.0.0.5] ([65.42.84.0]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KAA00HL3P2GS4B0@mail-amer.sun.com>; Thu, 13 Nov 2008 16:25:29 -0700 (MST) Date: Thu, 13 Nov 2008 17:29:21 -0600 From: Brian Cameron Subject: Re: codeina [LSARC/2008/709 FastTrack timeout 11/25/2008] In-reply-to: <1226617789.49887.302.camel@sr1-umpk-16> Sender: Brian.Cameron@sun.com To: John.Fischer@sun.com Cc: Brian Cameron , LSARC-ext@sun.com, desktop-discuss@opensolaris.org Message-id: <491CB851.5030203@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200811132243.mADMhYrE003702@sac.sfbay.sun.com> <1226617789.49887.302.camel@sr1-umpk-16> User-Agent: Thunderbird 2.0.0.16 (X11/20080922) Status: RO Content-Length: 2410 John: > 1. Does this project set a precedent in that we now > expect projects to provide KDE hooks? If so then > what are the said hooks? To be honest, I was unsure about whether we should distribute this file since we do not yet support KDE on Solaris. I do not have strong feelings about whether it should be included or not. I would be happy to remove it if ARC feels we should wait until KDE is more supported before including such files. Codina will still work for KDE users, it just will not automatically inform the users about plugin updates without the KDE specific desktop file. However, after receiving the update email, a KDE user could run codeina by hand to do the update, or just follow the steps in the email and download it via a web browser. > 2. How does this project deal with a user who switches > between SPARC and x86? How does this project deal > with a user who switches their Sun Ray server via > utswitch? What if the server was SPARC and is now x86? > Are the implications of this that the user would have > to purchase a new plugin? Would the difference in > system architecture cause the application to fail? > Would the difference in system architecture cause the > mechanism to overwrite the previous version? When you use the codeina application to login to the Fluendo server, you register your username and are given a password. Users can then freely re-download plugins that have been previously purchased. This is useful if the user accidently deletes the plugin or if the plugin has been updated (in which case the user should receive an email and codeina should automatically prompt the user to upgrade). However, each plugin license is only valid for one computer, so the user is expected to not abuse the license they agreed to when purchasing the plugin. In other words, users agree to not install the plugin on multiple machines. When a user replaces one machine with another, it is okay to migrate the license from one machine to another, as long as the same plugin license is not used on both. 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. Brian From Darren.Moffat@Sun.COM Fri Nov 14 04:01:43 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mAEC1hB7028957 for ; Fri, 14 Nov 2008 04:01:43 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mAEC1hIM000691 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Fri, 14 Nov 2008 04:01:43 -0800 (PST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KAB0010BO2TWS00@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 14 Nov 2008 05:01:41 -0700 (MST) Received: from gmp-eb-inf-1.sun.com ([192.18.6.21]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KAB00E3FO2S6JE0@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 14 Nov 2008 05:01:41 -0700 (MST) Received: from fe-emea-10.sun.com (gmp-eb-lb-2-fe2.eu.sun.com [192.18.6.11]) by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mAEC1dMX005978 for ; Fri, 14 Nov 2008 12:01:39 +0000 (GMT) Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KAB00501O1DB400@fe-emea-10.sun.com> (original mail from Darren.Moffat@Sun.COM) for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 14 Nov 2008 12:01:39 +0000 (GMT) Received: from [129.156.173.21] by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KAB0060CO2M8830@fe-emea-10.sun.com>; Fri, 14 Nov 2008 12:01:36 +0000 (GMT) Date: Fri, 14 Nov 2008 12:01:34 +0000 From: Darren J Moffat Subject: Re: codeina [LSARC/2008/709 FastTrack timeout 11/25/2008] In-reply-to: <491CB851.5030203@sun.com> Sender: Darren.Moffat@Sun.COM To: Brian Cameron Cc: John.Fischer@Sun.COM, Brian Cameron , LSARC-ext@Sun.COM, desktop-discuss@opensolaris.org Message-id: <491D689E.90603@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200811132243.mADMhYrE003702@sac.sfbay.sun.com> <1226617789.49887.302.camel@sr1-umpk-16> <491CB851.5030203@sun.com> User-Agent: Thunderbird 2.0.0.16 (X11/20080922) Status: RO Content-Length: 1717 Brian Cameron wrote: > When you use the codeina application to login to the Fluendo server, you > register your username and are given a password. Users can then freely > re-download plugins that have been previously purchased. This is useful if > the user accidently deletes the plugin or if the plugin has been updated (in > which case the user should receive an email and codeina should automatically > prompt the user to upgrade). > > However, each plugin license is only valid for one computer, so the user is > expected to not abuse the license they agreed to when purchasing the plugin. > In other words, users agree to not install the plugin on multiple machines. > When a user replaces one machine with another, it is okay to migrate the > license from one machine to another, as long as the same plugin license is > not used on both. > > 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. 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`. We have the same problem with Firefox but it at least has a workaround by allowing the user to set the $MOZ_PLUGIN_PATH variable. -- Darren J Moffat From Brian.Cameron@sun.com Fri Nov 14 13:47:43 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mAELlgal016420 for ; Fri, 14 Nov 2008 13:47:42 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id mAELlX9d020814 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Fri, 14 Nov 2008 21:47:41 GMT Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KAC00H0BF7FY600@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 14 Nov 2008 14:47:39 -0700 (MST) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KAC00E04F7FON20@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 14 Nov 2008 14:47:39 -0700 (MST) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mAELlduE004984 for ; Fri, 14 Nov 2008 21:47:39 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KAC00G01EY4BJ00@mail-amer.sun.com> (original mail from Brian.Cameron@Sun.COM) for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 14 Nov 2008 14:47:39 -0700 (MST) Received: from [10.0.0.5] ([65.42.84.0]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KAC00F2AF723E30@mail-amer.sun.com>; Fri, 14 Nov 2008 14:47:31 -0700 (MST) Date: Fri, 14 Nov 2008 15:51:19 -0600 From: Brian Cameron Subject: Re: codeina [LSARC/2008/709 FastTrack timeout 11/25/2008] In-reply-to: <491D689E.90603@Sun.COM> Sender: Brian.Cameron@sun.com To: Darren J Moffat Cc: John.Fischer@sun.com, Brian Cameron , LSARC-ext@sun.com, desktop-discuss@opensolaris.org Message-id: <491DF2D7.1080600@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200811132243.mADMhYrE003702@sac.sfbay.sun.com> <1226617789.49887.302.camel@sr1-umpk-16> <491CB851.5030203@sun.com> <491D689E.90603@Sun.COM> User-Agent: Thunderbird 2.0.0.16 (X11/20080922) Status: RO Content-Length: 1835 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 From Darren.Moffat@sun.com Mon Nov 17 02:21:40 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mAHALepL004685 for ; Mon, 17 Nov 2008 02:21:40 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mAHALcKi012771 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Mon, 17 Nov 2008 02:21:40 -0800 (PST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KAH00N0L3G41700@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 17 Nov 2008 02:21:40 -0800 (PST) Received: from gmp-eb-inf-2.sun.com ([192.18.6.24]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KAH00KYJ3FSS330@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 17 Nov 2008 02:21:39 -0800 (PST) Received: from fe-emea-09.sun.com (gmp-eb-lb-2-fe2.eu.sun.com [192.18.6.11]) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mAHALS9f029789 for ; Mon, 17 Nov 2008 10:21:28 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KAH004013A32X00@fe-emea-09.sun.com> (original mail from Darren.Moffat@Sun.COM) for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 17 Nov 2008 10:21:27 +0000 (GMT) Received: from [129.156.173.21] by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KAH00BLG3FIYZC0@fe-emea-09.sun.com>; Mon, 17 Nov 2008 10:21:20 +0000 (GMT) Date: Mon, 17 Nov 2008 10:21:18 +0000 From: Darren J Moffat Subject: Re: codeina [LSARC/2008/709 FastTrack timeout 11/25/2008] In-reply-to: <491DF2D7.1080600@sun.com> Sender: Darren.Moffat@sun.com To: Brian Cameron Cc: John.Fischer@sun.com, Brian Cameron , LSARC-ext@sun.com, desktop-discuss@opensolaris.org Message-id: <4921459E.8040709@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200811132243.mADMhYrE003702@sac.sfbay.sun.com> <1226617789.49887.302.camel@sr1-umpk-16> <491CB851.5030203@sun.com> <491D689E.90603@Sun.COM> <491DF2D7.1080600@sun.com> User-Agent: Thunderbird 2.0.0.16 (X11/20080922) Status: RO Content-Length: 1026 Brian Cameron wrote: > 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. IMO this is not a bug it is a fundamental architectural issue that must be resolved. Placing binaries into users home dirs requires that cross architecture issues must be resolved. Is if there is a way to have codeina install into the system wide GStreamer plugin directory. -- Darren J Moffat From Brian.Cameron@sun.com Mon Nov 17 11:05:59 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mAHJ5xv3018510 for ; Mon, 17 Nov 2008 11:05:59 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mAHJ5weg033524 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Mon, 17 Nov 2008 12:05:59 -0700 (MST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KAH00F1VRPXLJ00@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 17 Nov 2008 11:05:57 -0800 (PST) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KAH00DOURPWQH30@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 17 Nov 2008 11:05:56 -0800 (PST) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mAHJ5uAg023595 for ; Mon, 17 Nov 2008 19:05:56 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KAH00401R9PNJ00@mail-amer.sun.com> (original mail from Brian.Cameron@Sun.COM) for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 17 Nov 2008 12:05:56 -0700 (MST) Received: from [10.0.0.3] ([65.42.80.91]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KAH00AUIRPQJ680@mail-amer.sun.com>; Mon, 17 Nov 2008 12:05:51 -0700 (MST) Date: Mon, 17 Nov 2008 11:05:50 -0600 From: Brian Cameron Subject: Re: codeina [LSARC/2008/709 FastTrack timeout 11/25/2008] In-reply-to: <4921459E.8040709@Sun.COM> Sender: Brian.Cameron@sun.com To: Darren J Moffat Cc: John.Fischer@sun.com, Brian Cameron , LSARC-ext@sun.com, desktop-discuss@opensolaris.org Message-id: <4921A46E.30509@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200811132243.mADMhYrE003702@sac.sfbay.sun.com> <1226617789.49887.302.camel@sr1-umpk-16> <491CB851.5030203@sun.com> <491D689E.90603@Sun.COM> <491DF2D7.1080600@sun.com> <4921459E.8040709@Sun.COM> User-Agent: Thunderbird 2.0.0.16 (X11/20080922) Status: RO Content-Length: 2963 Darren: >> 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. > > IMO this is not a bug it is a fundamental architectural issue that must > be resolved. Placing binaries into users home dirs requires that cross > architecture issues must be resolved. Filing a bug with the upstream community is just a necessary step to getting the bug fixed upstream. I think your request that codeina install plugins to the user's $HOME directory in a way that supports cross architecture use is reasonable. Since GStreamer already supports the infrastructure, it is a small amount of work to fix codeina to work this way before we integrate. Would it be acceptable to approve this ARC case with the assertion that this issue will be fixed before codeina is integrated? > Is if there is a way to have codeina install into the system wide > GStreamer plugin directory. Yes, codeina does support a plugin mechanism so that a distro can specify that the plugin be installed in any fashion desired. However, to install to the system-wide GStreamer plugin directory, the user would obviously need access to the root password, or the RBAC role which allows package installation. We could, for example, get this to work via gnome-su or sudo and ask the user for the root password after purchasing the plugin if RBAC is not setup for the user to be able to install straightaway. Or we could tell the user "Set up RBAC and run codeina again". Since the user has already purchased the plugin, they are free to download it again as many times as they like with their Fluendo account username and password. However, I think it would be a mistake to set up codeina in this way. Remember that codeina is targeting novice end-users and not experienced system administrators. A system administrator should be clever enough to check the README information associated with the plugin to learn how to install it properly for system-wide use. Requiring the user to set up RBAC, or enter root passwords adds complication that is unnecessary, and somewhat defeats the purpose of having a program like codeina for novice users on the system. So, instead, I would prefer to just fix the way codeina installs files to the users $HOME directory to support cross architecture setups. Is this reasonable? Brian From Darren.Moffat@sun.com Tue Nov 18 04:20:14 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mAICKEhq022876 for ; Tue, 18 Nov 2008 04:20:14 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mAICKCV6029992 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Tue, 18 Nov 2008 04:20:14 -0800 (PST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KAJ004033LOCR00@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue, 18 Nov 2008 05:20:12 -0700 (MST) Received: from gmp-eb-inf-2.sun.com ([192.18.6.24]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KAJ00G213LNS0A0@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue, 18 Nov 2008 05:20:12 -0700 (MST) Received: from fe-emea-10.sun.com (gmp-eb-lb-2-fe3.eu.sun.com [192.18.6.12]) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mAICKBDK011486 for ; Tue, 18 Nov 2008 12:20:11 +0000 (GMT) Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KAJ00J0137IO100@fe-emea-10.sun.com> (original mail from Darren.Moffat@Sun.COM) for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue, 18 Nov 2008 12:20:11 +0000 (GMT) Received: from [129.156.173.21] by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KAJ00B3L3LG9O20@fe-emea-10.sun.com>; Tue, 18 Nov 2008 12:20:05 +0000 (GMT) Date: Tue, 18 Nov 2008 12:20:04 +0000 From: Darren J Moffat Subject: Re: codeina [LSARC/2008/709 FastTrack timeout 11/25/2008] In-reply-to: <4921A46E.30509@sun.com> Sender: Darren.Moffat@sun.com To: Brian Cameron Cc: John.Fischer@sun.com, Brian Cameron , LSARC-ext@sun.com, desktop-discuss@opensolaris.org Message-id: <4922B2F4.9080000@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200811132243.mADMhYrE003702@sac.sfbay.sun.com> <1226617789.49887.302.camel@sr1-umpk-16> <491CB851.5030203@sun.com> <491D689E.90603@Sun.COM> <491DF2D7.1080600@sun.com> <4921459E.8040709@Sun.COM> <4921A46E.30509@sun.com> User-Agent: Thunderbird 2.0.0.16 (X11/20080922) Status: RO Content-Length: 2436 Brian Cameron wrote: > > Darren: > >>> 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. >> >> IMO this is not a bug it is a fundamental architectural issue that >> must be resolved. Placing binaries into users home dirs requires that >> cross architecture issues must be resolved. > > Filing a bug with the upstream community is just a necessary step to > getting > the bug fixed upstream. I think your request that codeina install plugins > to the user's $HOME directory in a way that supports cross architecture use > is reasonable. Since GStreamer already supports the infrastructure, it > is a > small amount of work to fix codeina to work this way before we integrate. > > Would it be acceptable to approve this ARC case with the assertion that > this > issue will be fixed before codeina is integrated? That is equivalent to agreeing the the change in the spec so yes it is acceptable. If this was a full case it would be written as a TCR but since it is a fast-track is is just a change to the spec under review. > Requiring the user to set up RBAC, or enter root passwords adds > complication > that is unnecessary, and somewhat defeats the purpose of having a program > like codeina for novice users on the system. Except that on OpenSolaris binary distro the initial user has the RBAC "Primary Administrator" profile so they could do this. If this was a full case I'd be suggesting TCA for this, but since it is a fast-track I'll leave it to the project team to decided if they want to do this now in this case or later. > So, instead, I would prefer to just fix the way codeina installs files to > the users $HOME directory to support cross architecture setups. That is sufficient for me. -- Darren J Moffat From Brian.Cameron@sun.com Thu Nov 27 09:48:49 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mARHmmFe020365 for ; Thu, 27 Nov 2008 09:48:48 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id mARHmirJ018069 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Fri, 28 Nov 2008 01:48:47 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KB0001076T9W400@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.Com); Thu, 27 Nov 2008 09:48:45 -0800 (PST) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KB000MJT6T89M20@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.Com); Thu, 27 Nov 2008 09:48:44 -0800 (PST) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mARHmipJ007213 for ; Thu, 27 Nov 2008 17:48:44 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KB000C016RX9R00@mail-amer.sun.com> (original mail from Brian.Cameron@Sun.COM) for LSARC-ext@Sun.Com (ORCPT LSARC-ext@Sun.Com); Thu, 27 Nov 2008 10:48:44 -0700 (MST) Received: from [10.0.0.4] ([24.32.67.166]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KB000AUD6T31O00@mail-amer.sun.com>; Thu, 27 Nov 2008 10:48:43 -0700 (MST) Date: Thu, 27 Nov 2008 11:48:06 -0600 From: Brian Cameron Subject: Re: codeina [LSARC/2008/709 FastTrack timeout 11/25/2008] In-reply-to: <200811132243.mADMhYrE003702@sac.sfbay.sun.com> Sender: Brian.Cameron@sun.com To: Brian Cameron Cc: LSARC-ext@sun.com, desktop-discuss@opensolaris.org Message-id: <492EDD56.8080309@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200811132243.mADMhYrE003702@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.17 (X11/20081023) Status: RO Content-Length: 11961 I am closing this case as approved. The only issue that was raised was Darren Moffat's requirement that codeina support installing plugins in a cross-architectural fashion. This bug will be fixed before codeina is integrated into Solaris. In other words, codeina will install plugins in a manner so that the same user can install plugins for both x86 and Sparc to the same user $HOME directory and they will both be functional. I created bugster bug #6777437 to track this issue. Note that codeina needs marketing approval before we can integrate into Solaris. As the schedule for 09.04 is getting late, and marketing does not seem close to making a decision, it is looking less likely that this will integrate into the 09.04 release. Therefore, I plan to postpone actually fixing this bug until it is more clear that codeina will actually integrate into Solaris. Brian Brian Cameron wrote: > Template Version: @(#)sac_nextcase %I% %G% SMI > This information is Copyright 2008 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > codeina > 1.2. Name of Document Author/Supplier: > Author: Brian Cameron > 1.3 Date of This Document: > 13 November, 2008 > 4. Technical Description > > 1. Introduction > > 1.1. Project/Component Working Name: > > codina > > 1.2. Name of Document Author/Supplier: > > Brian Cameron > > 1.3. Date of This Document: > > 11/06/2008 > > 1.4. Name of Major Document Customer(s)/Consumer(s): > 1.4.1. The PAC or CPT you expect to review your project: > > Solaris PAC > > 1.4.2. The ARC(s) you expect to review your project: > > LSARC > > 1.4.3. The Director/VP who is "Sponsoring" this project: > > Robert O'Dea > > 1.4.4. The name of your business unit: > > Software - OPG > > 1.5. Email Aliases: > 1.5.1. Responsible Manager: > > leo.binchy@sun.com > > 1.5.2. Responsible Engineer: > > brian.cameron@sun.com > > 1.5.3 Marketing Manager: > > dan.robert@sun.com > > 1.5.4. Interest List: > > desktop-discuss@opensolaris.org > > 2. Project Summary > 2.1. Project Description: > > codeina is an Fleundo application written in Python which simplifies > the process for users to discover and install GStreamer multimedia > plugins on their system. > > 4. Technical Description: > 4.1. Details: > > codeina is a client application from the Fluendo company which steps > the user through the process of buying and installing GStreamer > multimedia codec plugins. It uses an embedded browser in the > application to talk to a web server. By default codeina on Solaris > only supports connecting to the Fluendo server. Once connected, the > user can navigate through web pages to select plugins to download and > install. > > The codeina application can be run in two ways: > > - As a standalone program. In this case, a full list of available > plugins are presented to the user. The user can select a plugin > and is stepped through the process of downloading and installing > the plugin. > > - GStreamer supports the GST_INSTALL_PLUGINS_HELPER environment > variable. If a user tries to play a media format that is not > supported by available installed GStreamer plugins, then it will run > the program specified in this environment variable. By ensuring that > the user's session has this environment variable set to > "/usr/bin/codeina", then the codeina program will be launched. > > GStreamer itself (in the gst-plugins-base module) can be configured > to use a default value when the environment variable is not set via > the gst-plugins-base configure --with-install-plugins-helper option. > This method would be used to ensure codeina is used when integrating > codeina into Solaris. > > When codeina is launched via these GStreamer mechanisms, codeina > checks a list of configured servers to see if any server has a plugin > available to play this media type. If not, then codeina just exits > and allows the application to inform the user the media type cannot > be played. > > If a plugin is found, then codeina steps through the process of > downloading and installing the plugin. If more than one plugin is > found, the user can select which plugin they wish to download > install. > > Some plugins may be free. In this case, the user can simply download > and install the plugin immediately. Other plugins may be available > only for a fee. This is typical with plugins that require a license > fee to use (such as WindowsMedia, MP3, MPEG-2, or MPEG-4). In this > situation, codeina presents the user with a webstore defined by the > server where the user can pay for the plugin (perhaps by credit card or > PayPal). Codina uses PyOpenSSL to support HTTPS secure web > interactions for navigating websites that require such billing. > > In addition, codeina provides an autostart feature so that codeina is > always run with the user session with the "-u --sleep 5" arguments. > This causes codeina to check with the server periodically to see if > there are any updates to any plugins previously downloaded via codina. > If so, then the user is stepped through the process of downloading and > installing the updates. > > By default, when codeina installs a plugin, it installs it to the > $HOME/.gstreamer/plugins directory so that the user immediately is able > to use the plugin. > > The codeina application also provide hooks so that a distro can provide > additional plugins from other web resources. This is managed via > codeina's "providers" files. By providing a "providers" file, a > distro can make available either free plugins or plugins that are for > sale. The providers file has hooks so that a distro can specify their > own installation plugin which will step the user through a specified > webstore purchasing process for billing. Though, this obviously > requires that the distro set up the webstore service and write a > installation plugin for codeina. > > codeina keeps track of each platform internally by keeping track of the > following variables which are set as follows on Solaris: > > OS_NAME = "SunOS" > ARCH_NAME = "sparc" or "i386" > DISTRO_NAME = "solaris" > DISTRO_VERSION = "any" > > These values are used in handshaking between the client and server in > order to identify which plugins are available for a given client. If, > for example, Sun were to set up a providers file which pointed to a > Sun specific server, then the server would need to be configured to > identify the Sun client using these parameters. > > Likewise codeina provides hooks so that a distro can customize how > plugins are installed if desired. > > Although some distros (such as Red Hat and Mandriva Linux) have made > us of such integration hooks (such as providers files), the interfaces > are not documented. Fluendo plans to make these interfaces more public > in the future so that it is easier for distros to integrate with > codeina. In the meantime they should be considered Volatile interfaces. > > 4.2. Interfaces: > > Exported Interfaces Stability Comments > --------------------------------------- ----------- ---------------- > SUNWcodeina Uncommitted Package name. > SUNWcodeina-root Uncommitted Package name. > /usr/bin/codeina Volatile Script for > starting > codeina > /usr/bin/codeina.bin Volatile The codeina > application > /usr/lib/python/2.4/vendor-packages/codeina Project Python > Private implementation > of codina > /usr/share/applications/codeina.desktop Volatile Desktop file > /usr/share/autostart/codeina-update-kde.desktop for when KDE is > the desktop > being used. > /usr/share/codeina Project Private > Private directory for > icons and logos > /etc/codeina/providers Volatile Providers > directory > /etc/codeina/providers/fluendo.xml Volatile Fluendo > providers file > /etc/xdg/autostart/codeina-update.desktop > $XDG_CONFIG_HOME/share/codeina Volatile User config > $HOME/.gstreamer-0.10/plugins Volatile GStreamer user > plugin > directory > > Imported Interfaces Stability Comments > --------------- --------------- ----------------------- > SUNWpython-libs Unstable LSARC 2005/506 > Python External PSARC/2005/532 Python > Evolving Migration from /usr/sfw > to /usr and upgrade to v2.4.x > GStreamer Volatile LSARC 2006/202 > Python XDG Uncommitted PSARC 2008/104 > SUNWgst-python Uncommitted PSARC 2008/105 > python-notify Uncommitted PSARC 2008/419 > PyYAML Uncommitted PSARC 2008/676 > PyOpenSSL Uncommitted > > 4.3. Doc Impact: > > Man page is needed. > > 4.4. Packaging & Delivery: > > SUNWcodeina, SUNWcodeina-root - packages for codeina. > > 4.5. Dependencies: > > None. > > 4.6. L10N Impact: > > The Desktop team and the G11N are working together to evaluate and > provide I18N/L10N support. > > 4.7. Security Impact: > > None. > > 5. Reference Documents: > > The codeina website: > https://core.fluendo.com/gstreamer/trac/wiki/codeina > > Other information about codeina: > http://fedoraproject.org/wiki/Multimedia/Codeina > http://fedoraproject.org/wiki/Releases/FeatureCodecBuddy > > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > Desktop > 6.5. ARC review type: FastTrack > 6.6. ARC Exposure: open > > _______________________________________________ > opensolaris-arc mailing list > opensolaris-arc@opensolaris.org