I‘m not a pro but some licenses state you need to provide the code, not necessarily „provide code in your package“ afaik. So you could put your github/lab/forge link and the license in the app and provide the rest in your repo? Not sure if thats how its done but it seem logical. Good luck.
That's what I am doing now too. I add the license text files in the app, document where to find and to what program it belongs to and provide a link where to get the source files. I have looked up each license and they allow distributing the binaries.
I feel like thats a sane solution.
And you can still contact the FSF so mail you a copy of the GPL ;D
That depends on the licenses. Saying they're libre is a classification, not specific.
Note also that source code may be licensed differently from binaries, assets/resources, etc.
Check the license of what you're obtaining and bundling specifically. To get an overview of licenses and their permissions and requirements, see https://choosealicense.com/
These are commandline applications, so there shouldn't be any problem I think. The binaries are also obtained precompiled from Archlinux repos and include license texts, which I now include in my AppImage. Only one application does not include license text in the package, but found the online repository. Now I download and bundle this license file, document where to get the source and link it. I looked up each license and they all explicitly allow distributing the binaries. Looks like I'm good to go.
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities !webdev@programming.dev
