Re: Attention anyone uploading binaries to ftp.gnome.org/pub/binaries - understand the GPL

[Colin Walters <walters verbum org>]

[Note to everyone: It turns out the big CC list triggered moderation, so
your messages may not go through if you also CC everyone.  I suggest
removing the CC list and replying just to desktop-devel-list]

On Thu, 2011-09-22 at 13:39 +0200, Mario Sanchez Prada wrote:
> On 09/21/2011 05:10 PM, Colin Walters wrote:
> > [...]
> > Please help me out here - win32/mac binary maintainers, add a better
> > example SOURCES file please.  And let me know what you think in general.
> 
> I added SOURCES file for the three Mac binaries of frogr up there in the
> FTP. I've tried to properly describe (with links when needed) the
> process of building the .dmg files from MacOSX with the gtk-osx project,
> but please let me know if you find something missing or wrong.

Thanks for taking a look at this, Mario.  Just for everyone else, here's
the SOURCES file we're discussing:
http://ftp.acc.umu.se/pub/GNOME/binaries/mac/frogr/0.6.1/SOURCES

The instructions look good to me.  However, there is one important issue
I see with the Source: line, and that comes down to the fact that the
binary .dmg file you have here embeds your app AND its dependencies (gtk
+, etc.).

  "Ige-mac-bundler copies all of the files you indicated in your bundle
file, and also pulls in the dependencies it can find, and it adjusts the
install paths to reflect the new locations."

After a little bit of searching around I was able to figure out how to
view the .dmg on Linux via dmg2img (http://vu1tur.eu.org/tools/):

And we can see here:

./frogr.app/Contents/Resources/lib/libatk-1.0.0.dylib
./frogr.app/Contents/Resources/lib/libcairo.2.dylib
./frogr.app/Contents/Resources/lib/libexif.12.dylib
./frogr.app/Contents/Resources/lib/libexpat.1.dylib
./frogr.app/Contents/Resources/lib/libfontconfig.1.dylib
./frogr.app/Contents/Resources/lib/libfreetype.6.dylib
./frogr.app/Contents/Resources/lib/libgailutil.18.dylib
./frogr.app/Contents/Resources/lib/libgcrypt.11.dylib
./frogr.app/Contents/Resources/lib/libgdk-quartz-2.0.0.dylib
./frogr.app/Contents/Resources/lib/libgdk_pixbuf-2.0.0.dylib
./frogr.app/Contents/Resources/lib/libgio-2.0.0.dylib
./frogr.app/Contents/Resources/lib/libglib-2.0.0.dylib
./frogr.app/Contents/Resources/lib/libgmodule-2.0.0.dylib
./frogr.app/Contents/Resources/lib/libgnutls.26.dylib
./frogr.app/Contents/Resources/lib/libgobject-2.0.0.dylib
./frogr.app/Contents/Resources/lib/libgpg-error.0.dylib
./frogr.app/Contents/Resources/lib/libgthread-2.0.0.dylib
./frogr.app/Contents/Resources/lib/libgtk-quartz-2.0.0.dylib
./frogr.app/Contents/Resources/lib/libigemacintegration.0.dylib
./frogr.app/Contents/Resources/lib/libintl.8.dylib
./frogr.app/Contents/Resources/lib/libjpeg.7.dylib
./frogr.app/Contents/Resources/lib/libpango-1.0.0.dylib
./frogr.app/Contents/Resources/lib/libpangocairo-1.0.0.dylib
./frogr.app/Contents/Resources/lib/libpangoft2-1.0.0.dylib
./frogr.app/Contents/Resources/lib/libpixman-1.0.dylib
./frogr.app/Contents/Resources/lib/libpng12.0.dylib
./frogr.app/Contents/Resources/lib/libsoup-2.4.1.dylib
./frogr.app/Contents/Resources/lib/libtasn1.3.dylib

You need to list the corresponding source code for *every one* of these
libraries.  Otherwise we have no idea - it's whatever version of gtk+
etc. happened to be installed on your workstation.

[Not all of these are under the GPL/LGPL, but many are, and it's just
good practice to link to the source code for MIT things anyways if you
care about FOSS]

Probably the best way to accomplish this would be to have
ige-mac-bundler generate the data for you, if it can't already.   From
what I understand of this whole process, jhbuild's "packagedb" has the
data, you could extract it from "jhbuild info".

I wasn't planning to work on jhbuild support for generating SOURCES
files until I had time to work on draining my huge queue of jhbuild
patches after GNOME 3.4 was released, but if it's helpful to you for
the OS X work I can take a look at it sooner.