-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Robert J. Hansen wrote: > Alexander K. Hansen wrote: >> The ETA is "when it's ready". > > After this long of a delay, I hope people can understand if I ask for a > little more precision than that. I don't object to a ship date of "when > it's ready and no sooner", but it would help if we could know precisely > what still remains to be done in order to make it ready.
I was literally ready to write up an e-mail about it last weekend but real life got in the way, and David Morrison needed some help with last minute Fink-upgrade stuff, and I decided to punt it until this weekend settles down. >> Ben has been running clean builds of the several hundred packages that >> will be affected by this update, to catch build problems, missing >> dependencies, ... so that users don't wind up with busted systems. > > Which packages are broken? Have the maintainers been informed? Who is > working on fixing these packages, and do they need help? They hadn't been informed because the majority of issues were systemic to the gtk upgrade, fink policy issues, fixing Shlibs fields and validation errors; often when issues were found it involved changing 50 packages with similar configuration stuff. It's much easier to just kind of do it all at once in batch. As of maybe 2 weeks ago, what's left is individual packages that need special attention, so it's time to get maintainers involved, but so much has changed I need to write up what all was involved in getting updated. It's a lot to wrap your head around. > Like Tristan, I am very willing to help with this process. But the > process appears to lack transparency, and that makes it difficult for > interested parties to do anything more than stand on the sidelines and > say "what's going on?" It lacked transparency early on 'cause it was such a daunting task it wasn't clear it'd even work, and by the time I knew it would, it was almost easier for us (me and a few others, who are involved day-to-day in #fink) to just barrel through and mass-update things. If there's anything I've learned from trying to get KDE to stable (which still is only about 80% done), it's hard to wrangle 20 maintainers into organizing on something, much less 100. :) On the other hand, I've been on the other side of open-source stuff and being myself annoyed by a lack of transparency, and for that I apologize. Really, for the last 6 months it's felt like "oh, just 1 more thing" over and over again to get things where they are. I assure you, it was not for lack of trying... :P - -- Benjamin Reed a.k.a. Ranger Rick Fink, KDE, and Mac OS X development http://www.racoonfink.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHITOLUu+jZtP2Zf4RAt1lAJ9GLKKdQ/0vMOs4/lbYF0EdeUFoUQCbB8IN VIpHbxVgPqMEa9DYVfOn9Mc= =XJZs -----END PGP SIGNATURE----- ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel
