On 05/23/2011 06:34 PM, Denys Vlasenko wrote:
On Mon, 2011-05-23 at 17:03 +0200, Jiri Moskovcak wrote:
>>>>> the only thing which has left to fix is
>>>>> getting the component name (problem_data.c: 129). I need to ask rpm
for
>>>>> it and there are few possible solution:
>>>>>
>>>>> 1. call abrt-action-save-package-data
>>>>> 2. $ rpm -qf executable
>>>>> 3. use librpm
>>>>>
>>>>> Suggestions?
>>>>
>>>> I propose to add abrt-action-save-package-data call to reporters.
>>>>
>>>
>>> - ok, Nikola is working on adding this to bz plugin
>>
>> I meant: we can do it by modifying abrt_event.conf.
>> No need to change bz plugin's code.
> - I think bugzilla (and probably all reporters) should have control over
> this - if some component is missing and we know how to create it then
> create it... to me this seems better then relying on config file
I don't know... it feels un-Unixy.
Unix way is "each tool does one job, and does it well".
With this principle, abrt-action-bugzilla should do one thing, that is,
submit bugs. Not peruse RPM database. It should not even know that RPM
database exists.
- well, it knows about component anyway, because it's a required field
for bugzilla and how about running the a-a-bugzilla manually without
this clever config?
- I was for calling abrt-action-save-package-data rather then linking
against rpm, this way other distros can just provide their own
a-a-save-package-data instead of hacking the code (which will work even
with your config fix)