search for: gplrequiresourcepostedpubl

...t life, they should be downloadable somewhere >> somehow. > > No you are minunderstanding the GPL. It turns out you are absolutely right. You only have provide modified source to users to whom you distribute derived work. Found it here: https://www.gnu.org/licenses/gpl-faq.en.html#GPLRequireSourcePostedPublic I stand corrected. Thanks! Valeri > > You are only required to provide source to those who got the binary > artifact(s). They then have the full GPL rights to further modify etc. > In many cases the binaries are distributed to everyone and then so is > the source. In other case...

...; Had I sent my friend a binary copy he/she would have had the right to > require me to also hand over the source. > > None of us would have any obligations to a 3rd party. > To back up Peter on this, here are some relevant links from the FSF. https://www.gnu.org/licenses/gpl-faq.html#GPLRequireSourcePostedPublic The GPL does not require you to release your modified version, or any part of it. You are free to make modifications and use them privately, without ever releasing them. This applies to organizations (including companies), too; an organization can make a modified version and use it internally wi...

On 06/14/18 10:00, Peter Kjellstr?m wrote: > On Thu, 14 Jun 2018 16:26:27 +0200 > Gianluca Cecchi <gianluca.cecchi at gmail.com> wrote: > ... >>>> The src.rpm for that kernel is probably available somewhere. >>> >>> I'm fairly certain you cannot download the SRPM for EUS kernels. >>> You might if you're a Red Hat customer paying for

On 2018-06-14, Valeri Galtsev <galtsev at kicp.uchicago.edu> wrote: > > It turns out you are absolutely right. You only have provide modified > source to users to whom you distribute derived work. Found it here: > > https://www.gnu.org/licenses/gpl-faq.en.html#GPLRequireSourcePostedPublic Not totally relevant to this thread, but relevant to repeating: since the code is still GPLv2, if RedHat shares its code with me, I can still redistribute freely, even though RedHat is not necessarily redistributing to the general public. RedHat can not prevent me from redistribution even thoug...

...18-06-14, Valeri Galtsev <galtsev at kicp.uchicago.edu> wrote: >> >> It turns out you are absolutely right. You only have provide modified >> source to users to whom you distribute derived work. Found it here: >> >> https://www.gnu.org/licenses/gpl-faq.en.html#GPLRequireSourcePostedPublic > > Not totally relevant to this thread, but relevant to repeating: since > the code is still GPLv2, if RedHat shares its code with me, I can still > redistribute freely, even though RedHat is not necessarily > redistributing to the general public. RedHat can not prevent me from...

...on. In this case, if you are distributing tsshara.tar.gz, you could do this by: * including all of the NUT source code in that archive, * include a patch file, and say where to get the base version of NUT, or * provide a link to the modified source code http://www.gnu.org/licenses/gpl-faq.html#GPLRequireSourcePostedPublic -- Charles Lepple clepple at gmail -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: blazer_usb.c.txt URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20140129/18f8487f/attachment.txt>

...ou are distributing tsshara.tar.gz, you could do this by: > > * including all of the NUT source code in that archive, > * include a patch file, and say where to get the base version of NUT, or > * provide a link to the modified source code > http://www.gnu.org/licenses/gpl-faq.html#GPLRequireSourcePostedPublic > ok, > -- > Charles Lepple > clepple at gmail > -- Charles Lepple clepple at gmail -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20140131/cb29526e/attachment.html>

Howdy all... Reading with interest the thread(s) about REvolution, package licensing and the requirements of the GPL. First of all, let me introduce myself?. ?I joined REvolution Computing in February, after working for nearly 4 years for Intel as an open source strategist and before that for 6 years at Sun, where I established the first corporate open source programs office. ?I'm a Member of