> To sum up for glibmm maintainers: at least the glibmm 2.6 [1] tarballs > have a > strange content making them twice as big as necessary and causing a > SIGPIPE on > Windows platform. The extracted files are however fine. > > The suggested course of action is to repackage the tarball, as suggested > by > Ross below.
I'm not convinced that there's anything wrong with the tarballs, and I don't know what we should do differently to make them work for you. Could you check the glibmm and gtkmm 2.8 ones to see whether it's a one-off thing? I have CCed the gtkmm win32 port maintainer - Cedric Gustin. I'd expect him to see this problem too. I know that we don't use the default tarball format, because that can't support long enough filenames: http://bugzilla.gnome.org/buglist.cgi?query=160244 You will always get a better response on a mailing list than from me personally. > Ross Golder wrote: >> You could be right. In that case, the best thing to do would probably be >> to contact the maintainers of the glibmm package, explain what you've >> found and ask them to re-package and re-upload their tarball. I've >> copied them in for their info. If they have any problems or questions >> about re-uploading a tarball, they can contact [EMAIL PROTECTED] >> for help and assistance. > > I guess your Cc'ing them should be sufficient for a first try. I'll wait a > week then I'll try to reach developers through [email protected] > > Please keep me informed on this subject to avoid uselessly mailing this > list. > > Thanks all for your time. > > Regards, > GISQUET Christophe > > [1] For reference, it is used through libxml++ by the developers of the > wormux > game ( http://www.wormux.org/wiki/en/index.php ) > > > > Murray Cumming [EMAIL PROTECTED] www.murrayc.com www.openismus.com _______________________________________________ gtkmm-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gtkmm-list
