http://www.placenet.org/benoit/index.php/ fr Wed, 12 Nov 2008 14:03:18 +0100 http://blogs.law.harvard.edu/tech/rss Dotclear http://www.placenet.org/benoit/index.php/post/2007/06/13/Indiana-patches urn:md5:84db67a6ce2fc2e01e885f7fdb6fc7a1 Wed, 13 Jun 2007 14:55:00 +0200 Benoît Dejean GNOME buggnomelibgtoppatchSUNsystem-monitor <p>Dear Sun Microsystems, I think your <a href="http://src.opensolaris.org/source/xref/jds/spec-files/trunk/patches/">patches</a> are bullshit. Please drop them or <a href="http://0pointer.de/blog/projects/project-indiana.html">as already suggested, do fork</a>. <br /> As the maintainer of system-monitor and libgtop, i have already rejected stupid patches from you. <a href="http://src.opensolaris.org/source/xref/jds/spec-files/trunk/patches/libgtop-01-solaris.diff">They</a> <a href="http://src.opensolaris.org/source/xref/jds/spec-files/trunk/patches/gnome-system-monitor-01-solaris.diff">contain</a> <a href="http://src.opensolaris.org/source/xref/jds/spec-files/trunk/patches/gnome-applets-03-make-multiload-network-available.diff">unkown</a> API changes and a lot of dead code. The <a href="http://src.opensolaris.org/source/xref/jds/spec-files/trunk/patches/libgtop-01-solaris.diff">libgtop patch</a> is the most scary. Here's a tip: libgtop code is OS specific (linux, bsd, solaris, etc have their own separate implementation) so copying linux code to solaris is obviously NOT going to work. <br /> I can see that some of your patches are actually OK, but your people don't seem to understand how we work. <br /> This reminds me of that private mail where you asked me to re-license libgtop to LGPL because you had some kind of packaging issues ... because you wanted to install libgtop in /foo/bar and instead of /foo/baz. Bad for you.</p>