On Thu, Aug 11, 2011 at 11:22:31AM -0700, Brian Murray wrote: > Whether or not apport should be left on post-release for crash reporting > is independent of the original question which in my mind was: > > "Should we provide Stable Release Updates for apport package hooks?" > > I say aye.
We did get sidetracked a bit. But I think the sidetrack showed that yes, there is potential utility with being able to do post-release updates. It appears one of the main complaints here is that updating the hooks ends up requiring updating the entire package, which can be excessive. For xorg, in part to help mitigate this particular issue, I split out the apport hooks into a separate package from xorg, which I named 'xdiagnose' to help convey to the user that the package is for diagnosing problems. xdiagnose is a relatively small package, and contains only troubleshooting tools; so, updates don't download gobs of stuff, and regression risks worst case is breaking diagnostic tools - a lot less worrisome than breaking X. I would suggest if there are other situations where a) we want to update apport hooks semi-liberally post-release, but b) the package they're attached to is overly large or risky to update, then it may make sense to consider breaking out the apport hooks to a separate package. Bryce -- ubuntu-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
