[Mono-dev] [PATCH] Upgrade RabbitMQ libraries to version 1.5.3

[Michael Barker]

> Now the specification file contains interface descriptions like this:
>
>> <field name="mechanism" type="shortstr">
>> selected security mechanism
>> <doc>
>> A single security mechanisms selected by the client, which must be
>> one of those specified by the server.
>> </doc>
>> ...
>> </field>
>
> The used and needed source code file autogenerated-api-qpid-0-8.cs now
> contains for example:
>
>>    /// <summary>
>>    ///
>>    ///       A single security mechanisms selected by the client, which must be
>>    ///       one of those specified by the server.
>>    ///
>>    /// </summary>
>>    string Mechanism { get; }
>
> The description was copied from the non-free specification (and no otherwise
> defined licensed for the documentation strings) into the generated C# interface
> definition.
>
> This makes this C# code as is non-free, too.
>
> This is exactly the same matter when developers implement RFC standards and copy
> documentation from it into their source. The license of the specification is not an
> open-source license.

Is patching the generator so that the document comments are not
present in generated code sufficient to clear the DFSG?  If so, I'll
look into that as the next thing I do.  Otherwise, could you give me
some pointers for any other things that I should look at.  I'll pass
this information onto the RabbitMQ guys too.

I've had a look over the QPid stuff and it appears that the python
client doesn't make use of generated code, but the Java, C++ and C#
version do, so I will check out their implementation too.

Regards,
Michael Barker.