4 ms·

If you're installing through a package manager, you're probably installing something built from source rather than downloaded as a binary from upstream.

grawprog 7y ago
Fair point on that. Still, the rest is somewhat unclear.
inetknght 7y ago
> If you're installing through a package manager, you're probably installing something built from source rather than downloaded as a binary from upstream. I didn't get that impression from linked Qt blog post. I parsed the blog post to mean any/all binaries built. Eg if you build your own binaries from the open source license, you can't distribute them without a commercial or distribution license. Likewise, you can't download Qt binaries without a Qt account. It effectively locks out anyone who's not a developer and doesn't want a Qt account but does want to install some pre-built open source software.
- distances 7y ago
  > I didn't get that impression from linked Qt blog post. I parsed the blog post to mean any/all binaries built. Eg if you build your own binaries from the open source license, you can't distribute them without a commercial or distribution license. They can't add such limitations without modifying the open source license, which they aren't doing.
- jupp0r 7y ago
  It sounds like dynamically linking is ok, but statically linking against Qt is not.
  - jcelerier 7y ago
    that is 10000% unrelated
    - jupp0r 7y ago
      Care to elaborate? You are distributing Qt binaries in one case, you aren't in the other.
      - jcelerier 7y ago
        why would dynamically linked binaries be Qt ones specifically ? every linux distro and a lot of apps do Qt rebuilds which aren't "official Qt framework binaries".
- regularfry 7y ago
  It's LGPL'd. They can't add that restriction. > The object code form of an Application may incorporate material from a header file that is part of the Library. You may convey such object code under terms of your choice, provided that, <...access to source code provisions...>
- detaro 7y ago
  > Eg if you build your own binaries from the open source license, you can't distribute them without a commercial or distribution license. Given it is a known open-source license, (L)GPL, this restriction is obviously impossible.

grawprog 7y ago

Fair point on that. Still, the rest is somewhat unclear.

inetknght 7y ago

> If you're installing through a package manager, you're probably installing something built from source rather than downloaded as a binary from upstream. I didn't get that impression from linked Qt blog post. I parsed the blog post to mean any/all binaries built. Eg if you build your own binaries from the open source license, you can't distribute them without a commercial or distribution license. Likewise, you can't download Qt binaries without a Qt account. It effectively locks out anyone who's not a developer and doesn't want a Qt account but does want to install some pre-built open source software.

distances 7y ago
> I didn't get that impression from linked Qt blog post. I parsed the blog post to mean any/all binaries built. Eg if you build your own binaries from the open source license, you can't distribute them without a commercial or distribution license. They can't add such limitations without modifying the open source license, which they aren't doing.
jupp0r 7y ago
It sounds like dynamically linking is ok, but statically linking against Qt is not.
- jcelerier 7y ago
  that is 10000% unrelated
  - jupp0r 7y ago
    Care to elaborate? You are distributing Qt binaries in one case, you aren't in the other.
    - jcelerier 7y ago
      why would dynamically linked binaries be Qt ones specifically ? every linux distro and a lot of apps do Qt rebuilds which aren't "official Qt framework binaries".
regularfry 7y ago
It's LGPL'd. They can't add that restriction. > The object code form of an Application may incorporate material from a header file that is part of the Library. You may convey such object code under terms of your choice, provided that, <...access to source code provisions...>
detaro 7y ago
> Eg if you build your own binaries from the open source license, you can't distribute them without a commercial or distribution license. Given it is a known open-source license, (L)GPL, this restriction is obviously impossible.