I believe that you don't have to distribute them directly, but you can just
make them available to download somewhere. Dropbox would be a perfect
candidate to host both the binaries as the source imo.
http://www.gnu.org/licenses/gpl-faq.html#AnonFTPAndSendSources
http://www.gnu.org/licenses/gpl-faq.html#SourceAndBinaryOnDifferentSites
On Sat, Mar 3, 2012 at 9:47 AM, niXman <i.nix...@gmail.com> wrote:
> 2012/3/3 Earnie Boyd <ear...@users.sourceforge.net>:
> > On Fri, Mar 2, 2012 at 4:45 PM, Joshua Boyce
> > <raptorfac...@raptorfactor.com> wrote:
> >>
> >> On Sat, Mar 3, 2012 at 5:13 AM, Luis Lavena <luislav...@gmail.com>
> wrote:
> >>>
> >>> On Fri, Mar 2, 2012 at 1:09 PM, niXman <i.nix...@gmail.com> wrote:
> >>> >
> >>> > I didn't upload sources and scripts cause nobody needs them. I didn't
> >>> > want to hide them =)
> >>> >
> >>> > BTW, Why should I duplicate sources avalilable from official sites?
> >>>
> >>> That is where GPL becomes annoying, but you should comply :-(
> >>>
> >>
> >> Yep, it can be quite frustrating sometimes. :(
> >>
> >>
> http://www.gnu.org/licenses/gpl-faq.html#DistributingSourceIsInconvenient
>
> It is very inconvenient, because for each archive with size of 30-60
> MB, I have to add an archive of sources with size of 150-180 MB.
> Besides, I doubt that the gcc/binutils/mingw-w64 projects will ever
> disappear completely, and there wouldn't be any possibility to
> download the necessary source code revision.
>
> Again, I have not uploaded the build scripts and sources for two reasons:
> 1. Until now nobody asked.
> 2. On google.code.com the space for the project is limited.
>
> but not for that to hide something from someone, or even with any
> malicious intent.
>
> But I agree with the fact that in every build the license files used
> for each project to be inserted. I will do so.
>
> >
> > So in a nut shell, it is *your* responsibility to provide the exact
> > source for the binary distribution, including libraries, if someone
> > asks for it. Not all licenses require source distribution when
> > distributing the binary but it is a common practice to do so anyway.
> > If you offer a binary on the internet you must provide the source on
> > the internet from a location or locations you control.
> >
> > --
> > Earnie
> > -- https://sites.google.com/site/earnieboyd
> >
> >
> ------------------------------------------------------------------------------
> > Virtualization & Cloud Management Using Capacity Planning
> > Cloud computing makes use of virtualization - but cloud computing
> > also focuses on allowing computing to be delivered as a service.
> > http://www.accelacomm.com/jaw/sfnl/114/51521223/
> > _______________________________________________
> > Mingw-w64-public mailing list
> > Mingw-w64-public@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
>
>
> --
> Regards,
> niXman
>
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
