> Hmm... we currently patch around a dozen of the projects we build. > (Some, like Python IIRC, don't apply for Linux). What does that mean for > relying on existing system packages?
I can imagine a slower and more buggy Chandler available via apt, a version which is hamstrung by bugs that aren't fixed and features that aren't implemented in the packages we rely on. When I put it that way, I know it doesn't sound that exciting, but I think a lot of potential techie users would still appreciate the effort. Do any of our patches create incompatibilities, or are they all bug fixes? To the extent that our patches are bug fixes, I think having a credible apt strategy might add incentive for our open source friends to put out bug fix releases of their packages with greater alacrity. It's hard to tell people, "We don't even bother building Debian packages, but you should update your Debian packages with these bug fixes faster!" Sincerely, Jeffrey _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
