I implemented something like this for xorg, so people can file bugs against 'xorg' without needing to know the correct video driver or whatever to post against. I actually found that using the description for this was not terribly reliable, and instead mostly parse the attachments - the Xorg.0.log is a much more reliable indicator of the driver in use.
Having gone through that, there's a couple problems I see with generalizing this for any package. First, like I said, parsing the description is unreliable. It's also going to require a hefty amount of heuristics code, probably too much to download as an AJAX javascript routine, and likely imposing too much load to do it server-side.
I think something in more of a decision-tree format (c.f. apport-symptoms or the Bug Q&A story) is going to work a lot better for this, and would suggest that as a better solution.
I implemented something like this for xorg, so people can file bugs against 'xorg' without needing to know the correct video driver or whatever to post against. I actually found that using the description for this was not terribly reliable, and instead mostly parse the attachments - the Xorg.0.log is a much more reliable indicator of the driver in use.
Having gone through that, there's a couple problems I see with generalizing this for any package. First, like I said, parsing the description is unreliable. It's also going to require a hefty amount of heuristics code, probably too much to download as an AJAX javascript routine, and likely imposing too much load to do it server-side.
I think something in more of a decision-tree format (c.f. apport-symptoms or the Bug Q&A story) is going to work a lot better for this, and would suggest that as a better solution.