Looking for example at git-lfs:
https://src.fedoraproject.org/rpms/git-lfs/blob/master/f/git-lfs.spec
I am afraid that the license field is wrong. Since the Go packages are statically linked, that means also content of all the BR is part of the binary packages and therefore should include their licenses. This also applies to Rust and all other statically linked packages.
I believe the guidelines should be amended to handle this scenario and all the packages fixed appropriately.
Thoughts?
Vít
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On Fri, 2020-06-26 at 13:33 +0200, Vít Ondruch wrote:
Looking for example at git-lfs:
https://src.fedoraproject.org/rpms/git-lfs/blob/master/f/git-lfs.spec
I am afraid that the license field is wrong. Since the Go packages are statically linked, that means also content of all the BR is part of the binary packages and therefore should include their licenses. This also applies to Rust and all other statically linked packages.
I think we already do it fine for Rust, no?
https://src.fedoraproject.org/rpms/rust-ripgrep/blob/master/f/rust-ripgrep.s... https://src.fedoraproject.org/rpms/rust-bat/blob/master/f/rust-bat.spec#_35 https://src.fedoraproject.org/rpms/rust-starship/blob/master/f/rust-starship...
and so on.
I believe the guidelines should be amended to handle this scenario and all the packages fixed appropriately.
We've also discussed this here: https://src.fedoraproject.org/rpms/rust-rpick/pull-request/1
Thoughts?
I think Pull Request is very welcomed in the packaging guidelines.
Vít
legal mailing list -- legal@lists.fedoraproject.org To unsubscribe send an email to legal-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/legal@lists.fedoraproject.org
- -- Igor Raits ignatenkobrain@fedoraproject.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On Fri, 2020-06-26 at 13:48 +0200, Igor Raits wrote:
On Fri, 2020-06-26 at 13:33 +0200, Vít Ondruch wrote:
Looking for example at git-lfs:
https://src.fedoraproject.org/rpms/git-lfs/blob/master/f/git-lfs.spec
I am afraid that the license field is wrong. Since the Go packages are statically linked, that means also content of all the BR is part of the binary packages and therefore should include their licenses. This also applies to Rust and all other statically linked packages.
I think we already do it fine for Rust, no?
https://src.fedoraproject.org/rpms/rust-ripgrep/blob/master/f/rust-ripgrep.s... https://src.fedoraproject.org/rpms/rust-bat/blob/master/f/rust-bat.spec#_35 https://src.fedoraproject.org/rpms/rust-starship/blob/master/f/rust-starship...
and so on.
Forgot to mention that we even have script to generate those: https://pagure.io/fedora-rust/rust2rpm/blob/master/f/tools/fedora-helper.py
I believe the guidelines should be amended to handle this scenario and all the packages fixed appropriately.
We've also discussed this here: https://src.fedoraproject.org/rpms/rust-rpick/pull-request/1
Thoughts?
I think Pull Request is very welcomed in the packaging guidelines.
Vít
legal mailing list -- legal@lists.fedoraproject.org To unsubscribe send an email to legal-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/legal@lists.fedoraproject.org
- -- Igor Raits ignatenkobrain@fedoraproject.org
Dne 26. 06. 20 v 13:54 Igor Raits napsal(a):
On Fri, 2020-06-26 at 13:48 +0200, Igor Raits wrote:
On Fri, 2020-06-26 at 13:33 +0200, Vít Ondruch wrote:
Looking for example at git-lfs:
https://src.fedoraproject.org/rpms/git-lfs/blob/master/f/git-lfs.spec
I am afraid that the license field is wrong. Since the Go packages are statically linked, that means also content of all the BR is part of the binary packages and therefore should include their licenses. This also applies to Rust and all other statically linked packages.
I think we already do it fine for Rust, no?
https://src.fedoraproject.org/rpms/rust-ripgrep/blob/master/f/rust-ripgrep.s...
https://src.fedoraproject.org/rpms/rust-bat/blob/master/f/rust-bat.spec#_35
https://src.fedoraproject.org/rpms/rust-starship/blob/master/f/rust-starship...
and so on.
Forgot to mention that we even have script to generate those: https://pagure.io/fedora-rust/rust2rpm/blob/master/f/tools/fedora-helper.py
Ah, nice. Thx for claficiation.
I believe the guidelines should be amended to handle this scenario and all the packages fixed appropriately.
But this point still stands IMO.
V.
We've also discussed this here: https://src.fedoraproject.org/rpms/rust-rpick/pull-request/1
Thoughts?
I think Pull Request is very welcomed in the packaging guidelines.
Vít
legal mailing list -- legal@lists.fedoraproject.org To unsubscribe send an email to legal-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:
https://lists.fedoraproject.org/archives/list/legal@lists.fedoraproject.org
-
Igor Raits -
Vít Ondruch