Red Hat Bugzilla – Bug 492048
Please activate the --with-moonlight parameter
Last modified: 2009-05-11 17:24:29 EDT
Description of problem:
At rpmfusion.org we are in the process of publishing moonlight. At the moment it compiles with custom Fedora's mono for being Silverlight 1 compatible.
For Silverlight 2 we'll need this mono compiler switch enabled for being able of generating the classes subset needed from the mono distribution into the moonlight distribution.
There is no patent potential problems here since there is not new external code neither any other kind of change in the way of compiling or using mono or the mono apps.
So, please, only activate this switch.
Before I do this, I'll check with fedora-legal. There is a change in compiling as you need to build smcs (silverlight mcs) which does call on code which potentially brings mono into patent problems.
Lifting FE-Legal. Using this flag is okay, moonlight itself is still not.
(In reply to comment #2)
> Lifting FE-Legal. Using this flag is okay, moonlight itself is still not.
Is the report discouraging moonlight available anywhere? I would be interested in study it. Thanks!
I'm not sure what you're asking for here.
moonlight should be fine in rpmfusion just not in main Ismael. Let the reviewing begin.
(In reply to comment #5)
> moonlight should be fine in rpmfusion just not in main Ismael.
Of course! If there exist a current guideline in Fedora it still applies.
My interest is, if possible, about helping to constructively clear the doubts on the potential Moonlight risks so the guidelines could be revised in the future.
In the short term I'm happy with this flag activated :-)
At the Oct. 2008 PDC Microsoft put at least parts of Silverlight under the Open Specification Promise. This is basically a convenant not to sue. If Red Hat Legal still feels there is an undue risk then at least we can say that things are moving in the right direction on Microsoft' part, promising not to sue us for implementing certain rather big parts.
Now the parts they put under the OSP is the XAML vocabulary specification, this means any third party could implement something that reads and writes XAML markup without getting sued. It is my understanding that Moonlight would fall under said catagory.
Tom is it Legals opinion that Moonlight extends beyond this scope?
Regardless, Microsoft promising not to sue us is a good first step, especially in a widely circulated MS press release.
On a sidenote, Paul how is the enablement coming along?
It's packaged. I've put all the moonlight stuff in a separate subpackage (mono-moonlight) and disabled PPC for now. I'll open a bug on that once koji has built everything
Moonlight is still not permissable in Fedora. The OSP does not change that.
This is in rawhide, F11.