[snip] On Tue, 2012-07-17 at 22:14 +0200, Dieter Verfaillie wrote: > That leaves just a folder, which is exactly what the bundle is > and always has been (for example: > http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.24/) > > An SDK, in my mind, adds all the tools, sources, patches, scripts, > etc used to build that bundle (or to be correct, the packages making > up the bundle) and a way for application writers to integrate with > that system (so they don't have to reinvent the wheel). Versions of > tools would be set in stone for a given branch (let's say gcc 4.6 for > whatever packages are considered part of GNOME 3.4 and it's > maintenance > releases, 4.7 for GNOME 3.6 etc). Not limited to gcc off course, but > *everything*. Application writer integrating with this system would > be able to generate their own "bundle" (think glade, gedit, whatever) > which can then be used to build real installers (using WiX, > NSIS, InnoSetup, whatever). > > Doing all this is the only way we can guarantee end users (of the > SDK) in the distant future will be able to patch say a 3 year old > GTK+ branch when nobody is left around to maintain it, provided said > user can get at a sufficiently old windows version (let's not pretend > current mingw build envs will just work on future windows versions, > see what happened when vista got released for example)...
I suggest that this is an idea for later, after we have what we had for GTK+ 2. Thanks for your efforts. -- Murray Cumming murr...@murrayc.com www.murrayc.com www.openismus.com _______________________________________________ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list