As we are currently having some huge , badly arranged output files (like firefox and totem) I want to push this bugreport again.
Alexander, did you try to split firefox.info into task related parts? - one possible solutions for this would be to use "XInclude" (example: [1]). The problem is that this technique has to be supported by bughelper and for this we have to edit the parsing of the info-files, with the result that feisty's bughelper.0.1 won't be compatible without codechanges
In my opinion the best solution would be to add an extra attribute "task" to the <clue>-element. We can implement explicit parsing of that attribute in the current version and work on a "output-per-task"-solution. bughelper.0.1 would just ignore that attribute and produce one output per .info-file.
As part of this changes we should think about a <description>-element to describe each task.
As we are currently having some huge , badly arranged output files (like firefox and totem) I want to push this bugreport again.
Alexander, did you try to split firefox.info into task related parts? - one possible solutions for this would be to use "XInclude" (example: [1]). The problem is that this technique has to be supported by bughelper and for this we have to edit the parsing of the info-files, with the result that feisty's bughelper.0.1 won't be compatible without codechanges
In my opinion the best solution would be to add an extra attribute "task" to the <clue>-element. We can implement explicit parsing of that attribute in the current version and work on a "output- per-task" -solution. bughelper.0.1 would just ignore that attribute and produce one output per .info-file. -element to describe each task.
As part of this changes we should think about a <description>
Any ideas, suggestions?
Markus
[1] http:// www.zvon. org/xxl/ XIncludeTutoria l/Output/ example12. html