Hi Tobias, > At least assaultcube-data needs to go to non-free. The engine could go > to contrib if everything required for it it is free software. > > I strongly suggest that you use keep old packaging scheme (two source > packages, assaultcube and assaultcube-data) > > I'm not sure at all if putting the data on a git repository would > violate their license. (it is not unmodified distribution then) > > Srry, I think I have to throw in towel for that package… > Please seek advice from debian-legal. I kept the old packaging scheme by separating 'assaultcube (contrib) [1]' and 'assaultcube-data (non-free) [2]' without violating copyright. Please could you analyze my two packages. :) [1] https://mentors.debian.net/package/assaultcube [2] https://mentors.debian.net/package/assaultcube-data Thanks! -- ⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao] ⣾⠁⢠⠒⠀⣿⡁ Debian Wiki: https://wiki.debian.org/coringao ⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780 ⠈⠳⣄⠀⠀⠀ 2157 630B D441 A775 BEFF D35F FA63 ADA6 B638 B780
Attachment:
signature.asc
Description: This is a digitally signed message part