Slashdot Mirror


Does Shareware X-Chat for Windows Violate the GPL?

pc486 writes "The popular IRC client X-Chat has recently come under criticism as to whether or not the new shareware Windows version of the IRC client violates the GPL. All sorts of points are being persued, such as pure GPL Gettext linking, gtk translation worries, copyright issues, who's code is what and more." This is a complicated tale of GPL licensing, so beware.

1 of 594 comments (clear)

  1. Even easier to read, feat. clickable links ;) by KAMiKAZOW · · Score: 1, Redundant

    About Windows release licensing.

    peterz Joined: 09 Jun 2004 Posts: 125 Location: Australia PostPosted: Sun Aug 29, 2004 6:44 am Post subject: About Windows release licensing.

    Hi All, I'd just like to make a few short points, so I don't have to repeat them to those who have asked.

    1) A GPL source code will continue to be available. 2.4.1, 2.4.2... will have a GPL source for *nix on this web page.

    2) My particular Windows release is not released under GPL. Since people's source (patch) contributions have not stated any terms, I have decided to release this under Shareware, to protect the extra work I have done to make a good Windows release. However, I'll always respect peoples wishes. If someone has contributed some code and want it removed, you only have to ask (mail me personally), and it will be done. If this happens, I'll just rewrite the code myself, AND release it under GPL for your pleasure.

    3) You can download and use 3rd party builds (like SilvereX's). It's also worth noting that alot of the knowledge needed to create SilvereX's build comes directly from me.
    -- Peter.

    graspee Joined: 29 Aug 2004 Posts: 2 PostPosted: Sun Aug 29, 2004 1:58 pm Post subject Reply with quote

    Since people's source (patch) contributions have not stated any terms, I have decided to release this under Shareware

    It doesn't matter that people's contributions did not state any terms, they were contributing to a GPLd program.

    kev^ Joined: 22 Jul 2004 Posts: 6 Location: Montreal QC CA PostPosted: Sun Aug 29, 2004 4:44 pm Post subject: Reply with quote

    Quote:
    It's also worth noting that alot of the knowledge needed to create SilvereX's build comes directly from me.

    So basically you're saying you could kill the competition to make your release of the windows port exclusive. That's fine. Nothing's stopping me from keeping these old versions that I got and work. I refuse to get a program which shifted from a GPL-licensed program to Shareware. This shows the sole purpose of the writer changed from a personal project to something to help you financially. I'm sure you work as hard on the linux ports as on the windows. Surely not the same things are demanded but both got your equal effort but you're asking for profit from ONE of them.

    Ganf Joined: 29 Aug 2004 Posts: 3 PostPosted: Sun Aug 29, 2004 5:31 pm Post subject: Reply with quote Quote :

    My particular Windows release is not released under GPL Isn't it based on gettext ? gettext is GPL, every software wich depends on gettext *HAVE* to respect GPL. Question is : does your Windows build use gettext ? If you answer yes you *can't* release your build on another licence than GPL. When I download source I have a INSTALL.w32 which let me think you *are* depending on GPL code you don't own (eg. gettext). So ...

    tresni Joined: 29 Aug 2004 Posts: 1 PostPosted: Sun Aug 29, 2004 5:39 pm Post subject: Reply with quote Ganf wrote:

    Quote:
    My particular Windows release is not released under GPL Isn't it based on gettext ? gettext is GPL, every software wich depends on gettext *HAVE* to respect GPL. Question is : does your Windows build use gettext ? If you answer yes you *can't* release your build on another licence than GPL. When I download source I have a INSTALL.w32 which let me think you *are* depending on GPL code you don't own (eg. gettext). So ...

    Um... No.. The only thing he would be required to release would be any modifications to gettext, an