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

Sean Whitton spwhitton at spwhitton.name
Tue Aug 23 23:02:39 BST 2022


Hello,

On Tue 23 Aug 2022 at 09:10AM +03, Sebastian Dröge wrote:

>
> On Mon, 2022-08-22 at 11:31 +0300, Sebastian Dröge wrote:
>>
>> [...]
>>
>> With that we would be at exactly the same problem as gtk-sharp2 or
>> vala: could just include the correct .gir files in the source
>> packages.
>
> Sean, in bug #1017890 you wrote that simply using "a subset of the
> preferred form for modification", or in clearer words "information that
> was directly extracted from the preferred form of modification" would
> be acceptable.

Not quite what I said -- for that particular package, it seemed to me
that the way in which a subset was taken did not mean that the files
were no longer in their preferred form for modification.  It is surely
not the case that *any* subset of the preferred form for modification of
any source file is still the preferred form for modification :)

> In that case we could go here with shipping the .gir XML files with
> the Rust source packages plus shipping some compatible version of the
> code generator in the archive.
>
> If that is the ftp-master consensus then we would've found a way
> forward here. Can you confirm that?

It sounds plausible if the .gir files are just a subset in the way that
those files in the other package are -- again, it's case-by-case, and I
haven't looked at these files.

I suggest you explain in README.source why you think the .gir files are
still in their preferred form for modification.  Then the person looking
at the package in NEW can assess that.

-- 
Sean Whitton
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 869 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/attachments/20220823/2afbd57e/attachment-0001.sig>


More information about the Pkg-rust-maintainers mailing list