Slashdot Mirror


QT/GPL licensing trouble

Bitscape writes "LWN reports that Corel's gui packager, which uses both QT and lib-apt, fell under a licensing conflict which makes it illegal to distribute. While the author of lib-apt has agreed put an exception in its license for this case, is it a taste of things to come for people who use code released under the ever-expanding mess of incompatible licenses? "

4 of 388 comments (clear)

  1. Hang on, the situation has changed...? by teraflop+user · · Score: 5

    I think the situation has changed since this debate originally arose.

    The QT and GPL licenses certainly are potentially in conflict, but whether they are actually in conflict depends on current practice.

    IIRC, the GPL contains a clause which allows software to be linked with non-GPL packages if those packages are routinely supplied as part of the OS. Hence you can GPL a Windows application, and you can link applications with Xfree86 which is not GPL.

    Now every major Linux distribution is shipping QT and KDE, doesn't QT now fall under this same exception?

  2. Not quite.. by Kitsune+Sushi · · Score: 5

    RMS doesn't want people to stop using LGPL, period. As outlined by the link you provided, he only wants the LGPL to be used when its of strategic advantage (that is, it benefits free software more than it hurts it) to usher in the software in question into being a de facto standard across the board. the GNU C Library is a perfect example of this. Everybody has their own version of a C Library. glibc isn't anything special in this regard. LGPL it, however, and you'll have everyone using it because it's easier than brewing your own. It also ensures that more programs calling on that library will be compatible here and elsewhere without much modification.

    What RMS doesn't want to see, however, is software that gives free software a definitive edge (that is, if it does something much better than existing software, or something completely different -- and naturally you'd want the OS to be GPL'ed, duh) being LGPL'ed (which is why I'm still wondering why the Berlin Consortium chose the LGPL.. the proprietary Unices -- and free ones -- currently have X. Berlin would give free Unices an edge if it were GPL'ed.. oh well), because that doesn't help free software.

    --

    ~ Kish

  3. LWN admits error (Daniel M. Duley) by Anonymous Coward · · Score: 5

    I just got an email from Elizabeth O. Coolbaugh at LWN about this article, which has several falsehoods (you really can't link BSD or other licenses to GPL code, and it totally disregards the LGPL), and she said it is a misleading article and will be corrected. She also said it was "Obviously put together too quickly" ;) This is the reason Gnome for example uses almost entirely LGPL instead of GPL. The article took a rare exception to this. Using the GPL instead of LGPL for a library expressly means you want to deny linking to any non-GPL code (including BSD).
    Daniel M. Duley
    mosfet@jorsm.com Sorry, I don't have an account and Slashdot hasn't sent me a password yet ;-)

  4. Risking my Karma by DonkPunch · · Score: 5

    This line from the article made me a little tense:

    Please think seriously before you create a unique license for your software product. Please use the GPL or the BSD style license if you can.

    I don't want to overreact. I understand that the author is simply trying to encourage the use of established Open Source licenses. In fact, it has been my personal experience that many developers who fear the GPL don't entirely understand it ("The GPL causes me to sign over my copyright to the FSF. I can't modify my own program and sell it closed-source to someone later.")

    But I want to make a simple point -- the developer has an absolute right to determine the license under which his/her product is released. If Joe Programmer releases the most killer Linux app ever, but his license agreement requires you to hop on one foot to the mailbox and mail him a check once a month, then you either start hopping or you don't use the program. You can send Joe nasty emails, you can publicly flame him on slashdot, but none of that changes Joe's right to use his General Hopping License. If you can't handle the GHL, Joe's product is useless to you.

    --

    Save the whales. Feed the hungry. Free the mallocs.