From: Ralf Glaser <glaser@iotmaxx.de>
To: Michael Olbrich <m.olbrich@pengutronix.de>
Cc: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] python3 license
Date: Mon, 11 Nov 2024 09:45:33 +0000 [thread overview]
Message-ID: <BEZP281MB33614C99D919900E5FEC528CA5582@BEZP281MB3361.DEUP281.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <Zy3ZV2XTi4I8gsvn@pengutronix.de>
Hi,
i would have send a patch if i was able to understand the actual licensing...
Buildroot uses "Python-2.0, others" yocto only has "PSF-2.0", which both looks incomplete to me.
Best regards,
Ralf
________________________________________
Von: Michael Olbrich <m.olbrich@pengutronix.de>
Gesendet: Freitag, 8. November 2024 10:26
An: Ralf Glaser <glaser@iotmaxx.de>
Cc: ptxdist@pengutronix.de <ptxdist@pengutronix.de>
Betreff: Re: [ptxdist] python3 license
Hi,
On Thu, Nov 07, 2024 at 02:07:20PM +0000, Ralf Glaser wrote:
> is there a reason why the python3 rule does not contain license information?
No specific reason, beyond nobody created a patch for it so far.
Probably because it's not trivial. With a quite glace, I can see multiple
MIT and BSD style licenses besides the Python license itself.
A patch for that is of course welcome.
Michael
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2024-11-11 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 14:07 Ralf Glaser
2024-11-08 9:26 ` Michael Olbrich
2024-11-11 9:45 ` Ralf Glaser [this message]
2024-11-11 11:02 ` Michael Olbrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BEZP281MB33614C99D919900E5FEC528CA5582@BEZP281MB3361.DEUP281.PROD.OUTLOOK.COM \
--to=glaser@iotmaxx.de \
--cc=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox