I want to create an AppImage of my Python software and distribute it this way. The script will be compiled with Nuitka to include Python and Standard Library functionality. In the AppImage I want to bundle it with other Libre software, but in binary format downloaded from Arch package repos, as my script depends on them. My script is more like a complex automation tool. I do not make any changes to the code of these binary dependencies, just include them as they are.

I don’t know how to deal with the licenses. Do I have to include the license for every project in my AppImage? Do I have to put the source code of these projects in it too?

  • haui@lemmy.giftedmc.com
    3·
    10 months ago

    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.

    • thingsiplay@beehaw.orgOP
      3·
      10 months ago

      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.

  • Kissaki@programming.devEnglish
    2·
    10 months ago

    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/

    • thingsiplay@beehaw.orgOP
      2·
      10 months ago

      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.