Hello: The couple of guys maintaining KVIrc package this is, Kai and me, reckoned recently of a GPL version mismatch between the licence intended to apply to the whole project and the version which each source file is licensed under. We overlooked this problem for some time until the definite notice was given by Eugene Lyubimkin when we request sponsorship from him. Upstream guys have been quite receptive with our license requests, but we are not very fond of license stuff and we are not sure how to hint them. This is how licences are currently arranged in KVIrc: · Project license: GPLv2 adding openssl exception. · Source files in project: almost all GPLv2+, plus a small leftout amount with miscellaneous licenses. Maybe I'm just misleaded but I think it's somewhat confusing having a project license different to each of the project source. Ideally I would use GPLv2+ for everything, i.e., project and source files. The point is that GPLv2+ is IMHO perfectly valid for those source files, but not for the project due the fact that it links against OpenSSL. Even if upstream would be willing to relicense project under GPLv3, they wouldn't be able due to OpenSSL license incompatibility. There is work in progress to remove OpenSSL related code, but this will take time. Meanwhile we'd like to provide some more uploads, and advice upstream about licensing. There is also the option of considering GPLv2 for all, but KVIrc links against Qt4 and I'm not sure how this move would affect in this case. What do you think about this situation? what do you think would be the best or simplest solution? Thanks a lot, -- Raúl Sánchez Siles ----->Proud Debian user<----- Linux registered user #416098
Description: This is a digitally signed message part.