[Question]Guide on Licensing for Build Artifacts #2610
Unanswered
mochimochiki
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Question
I believe it's fantastic that
flet build
can generate executable files for each operating system. When considering the scenario of "distributing" these executable files, there are numerous dependent modules that should be distributed along with the artifacts. For instance, if I generate anexe
usingflet build windows
, the distribution offlutter_windows.dll
andvcruntime140.dll
and etc... is necessary for its execution. Additionally, proper licensing documentation (in some cases, source code) for flet and any additional dependent packages is essential. While compliance with licenses is the responsibility of the developer, having a guide can be immensely helpful. It seems like Kivy has prepared a guide on Package licensing. For instance, I am unsure which among the packages installed alongside flet will actually be "distributed" with the artifacts. Below is the result ofpip-licenses
immediately after installingflet v0.19.0
. The licenses to adhere to may vary depending on the packages that are "distributed" (e.g.,text-unidecode
orchardet
).pip-licenses results
Code sample
No response
Error message
No response
------------------------------------------------------
Beta Was this translation helpful? Give feedback.
All reactions