[Pkg-rust-maintainers] rust-gestreamer-player sys license questions

[matthias.geiger1024 at tutanota.de]

Chiming in into the discussion. As I am the one who packaged gstreamer-player in the first place, I'd like to know what the consensus of all this is. What is the solution to this problem when it comes to .gir generated code? I'd like the following as possible solution for this mess:

-Ship the .gir with the rust lib (separate or same package)
-ship the code generator for .gir to .rs
- still upload the rust lib on it's own
While this is feasible, I also doubt this would be scaleable since all GTK rust crates are generated by .gir files. This would mean a lot of extra work for me when packaging since there woul be "two" packages. As a logical consequence all libraries generated by .gir files (not just rust ones) would have to be amended/reuploaded. 
I have to agree with slomo that this could be viewed as somewhat inconsequential since some other packages (e.g. vala ) do exactly the same and this hasn't been an issue.
If this is the ftpmasters final decision, so be it. I will abide the rules to get the GTK rust stack into debian.

I hope the solution I pointed out above works for all. Certainly it would introduce (in my opinion) unnecessary  packages into debian. But if that's required by the policy, I'll follow it. 

--
Matthias Geiger (werdahias) 



25. Aug. 2022, 07:19 von spwhitton at spwhitton.name:

> Hello,
>
> On Thu 25 Aug 2022 at 10:47AM +03, Sebastian Dröge wrote:
>
>>
>> On Wed, 2022-08-24 at 15:20 -0700, Sean Whitton wrote:
>>
>>>
>>> I'm afraid I cannot respond to a message of this length.  As I mentioned
>>> previously, all the ftpteam really have the bandwidth to do is process
>>> what's in NEW.
>>>
>>
>> No worries, I understand that you're all having too much to do already
>> and thanks for taking your time anyway and doing such an ungrateful
>> job. I also have better things to do than discussing such nonsense.
>>
>> I guess a good summary of my mail would be exactly that: this process
>> is completely dysfunctional and doesn't scale.
>>
>
> s/completely/<something slightly weaker>/, because NEW works fine for a
> lot of other classes of package, and we definitely agree.
>
> -- 
> Sean Whitton
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/attachments/20220826/f70c54a5/attachment-0001.htm>