3 ms·

They have to be made available. You can ship a binary with a link to the code for example. But I do believe it's supposed to be available from the day the binar

by nkassis 15y ago

They have to be made available. You can ship a binary with a link to the code for example. But I do believe it's supposed to be available from the day the binaries are out.

rimantas 15y ago
But I do believe it's supposed to be available from the day the binaries are out. So, does anyone knows for sure?
- sp332 15y ago
  http://lmgtfy.com/?q=GNU+LGPL&l=1 http://lmgtfy.com/?q=GNU+LGPL&l=1
  - rimantas 15y ago
    And this helps how exactly? I know what GPL and LGPL is, I was asking, why few there "believe" and "think" instead of quoting.
- jrockway 15y ago
  "4. You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange." "Accompany it" is the key phrase. The source needs to be released at the same time as the binaries.
  - allwein 15y ago
    Apparently you stopped reading to soon. Section 6 states: " As an exception to the Sections above, you may also compile or link a "work that uses the Library" with the Library to produce a work containing portions of the Library, and distribute that work under terms of your choice, provided that the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications. You must give prominent notice with each copy of the work that the Library is used in it and that the Library and its use are covered by this License. You must supply a copy of this License. If the work during execution displays copyright notices, you must include the copyright notice for the Library among them, as well as a reference directing the user to the copy of this License. Also, you must do one of these things:" And 6B specifically says: "b) Accompany the work with a written offer, valid for at least three years, to give the same user the materials specified in Subsection 6a, above, for a charge no more than the cost of performing this distribution." So, since Apple is not distributing just the library binary on its own, but rather as part of Safari, Section 6 excepts Section 4. And all they must do, according to 6B, is accompany the work with a written offer (which it does, see Settings/General/Legal) to provide the source. Since no one has specified that they've written to Apple and been denied, they are not in violation of the license.
    - aplusbi 15y ago
      I think you are misinterpreting section 6. Section 6 is about the requirements for software that use the library. Specifically section 6 is about software that statically links to the library (section 5 is about dynamic linking). If you statically link to the library, the resulting binary contains the library and you are required to provide object files so that a user can relink with a different (and hopefully compatible) version of the library. In the case of Apple, they have made modifications to the library itself. They are then using the library, with modification, in Safari. Safari can be released under any license as outlined in section 5/6 but not the modifications. Those need to be released.
    - deleted 15y ago
      [deleted]

by nkassis 15y ago

They have to be made available. You can ship a binary with a link to the code for example. But I do believe it's supposed to be available from the day the binaries are out.

rimantas 15y ago

But I do believe it's supposed to be available from the day the binaries are out. So, does anyone knows for sure?

sp332 15y ago
http://lmgtfy.com/?q=GNU+LGPL&l=1 http://lmgtfy.com/?q=GNU+LGPL&l=1
- rimantas 15y ago
  And this helps how exactly? I know what GPL and LGPL is, I was asking, why few there "believe" and "think" instead of quoting.
jrockway 15y ago
"4. You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange." "Accompany it" is the key phrase. The source needs to be released at the same time as the binaries.
- allwein 15y ago
  Apparently you stopped reading to soon. Section 6 states: " As an exception to the Sections above, you may also compile or link a "work that uses the Library" with the Library to produce a work containing portions of the Library, and distribute that work under terms of your choice, provided that the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications. You must give prominent notice with each copy of the work that the Library is used in it and that the Library and its use are covered by this License. You must supply a copy of this License. If the work during execution displays copyright notices, you must include the copyright notice for the Library among them, as well as a reference directing the user to the copy of this License. Also, you must do one of these things:" And 6B specifically says: "b) Accompany the work with a written offer, valid for at least three years, to give the same user the materials specified in Subsection 6a, above, for a charge no more than the cost of performing this distribution." So, since Apple is not distributing just the library binary on its own, but rather as part of Safari, Section 6 excepts Section 4. And all they must do, according to 6B, is accompany the work with a written offer (which it does, see Settings/General/Legal) to provide the source. Since no one has specified that they've written to Apple and been denied, they are not in violation of the license.
  - aplusbi 15y ago
    I think you are misinterpreting section 6. Section 6 is about the requirements for software that use the library. Specifically section 6 is about software that statically links to the library (section 5 is about dynamic linking). If you statically link to the library, the resulting binary contains the library and you are required to provide object files so that a user can relink with a different (and hopefully compatible) version of the library. In the case of Apple, they have made modifications to the library itself. They are then using the library, with modification, in Safari. Safari can be released under any license as outlined in section 5/6 but not the modifications. Those need to be released.
  - deleted 15y ago
    [deleted]