Hi,
I little while ago I worked on a feature for systemtap where we could use abrt-action-install-debuginfo-to-abrt-cache to automatically download the required debuginfo to run a given script, by providing the build ID. I came across a couple bugs, specifically:
https://bugzilla.redhat.com/show_bug.cgi?id=730107 https://bugzilla.redhat.com/show_bug.cgi?id=726192
These appear to have been fixed, so I was planning on testing them out. I noticed, after upgrading to the most recent ABRT, that abrt-action-install-debuginfo-to-abrt-cache was moved to /usr/libexec/ from /usr/bin/.
I was just wondering if this should work the same way as before, or is it meant to be executed indirectly though something else in /usr/bin/ ?
Thanks, Chris
On 01/19/2012 04:23 PM, Chris Meek wrote:
I little while ago I worked on a feature for systemtap where we could use abrt-action-install-debuginfo-to-abrt-cache to automatically download the required debuginfo to run a given script, by providing the build ID. I came across a couple bugs, specifically:
https://bugzilla.redhat.com/show_bug.cgi?id=730107 https://bugzilla.redhat.com/show_bug.cgi?id=726192
These appear to have been fixed, so I was planning on testing them out. I noticed, after upgrading to the most recent ABRT, that abrt-action-install-debuginfo-to-abrt-cache was moved to /usr/libexec/ from /usr/bin/.
I was just wondering if this should work the same way as before, or is it meant to be executed indirectly though something else in /usr/bin/ ?
I don't know why, but other guys on my team just LOVE moving stuff out of /usr/bin to less accessible directories. I think it's counter-productive, and you just provided a real life example why. Thanks! :)
On 01/20/2012 09:37 AM, Denys Vlasenko wrote:
On 01/19/2012 04:23 PM, Chris Meek wrote:
I little while ago I worked on a feature for systemtap where we could use abrt-action-install-debuginfo-to-abrt-cache to automatically download the required debuginfo to run a given script, by providing the build ID. I came across a couple bugs, specifically:
https://bugzilla.redhat.com/show_bug.cgi?id=730107 https://bugzilla.redhat.com/show_bug.cgi?id=726192
These appear to have been fixed, so I was planning on testing them out. I noticed, after upgrading to the most recent ABRT, that abrt-action-install-debuginfo-to-abrt-cache was moved to /usr/libexec/ from /usr/bin/.
I was just wondering if this should work the same way as before, or is it meant to be executed indirectly though something else in /usr/bin/ ?
I don't know why, but other guys on my team just LOVE moving stuff out of /usr/bin to less accessible directories. I think it's counter-productive, and you just provided a real life example why. Thanks! :)
/usr/libexec is for application which are not meant to be run from cmdline in usual cases. So it's not because we "LOVE to move stuf out from /usr/bin" we HATE polluting /usr/bin with executables which are used in 99.9% cases only as helpers.
Chris, abrt-action-install-debuginfo-to-abrt-cache is just a wrapper for abrt-action-install-debuginfo to make it run with SGID. If you just want to download the debuginfo packages for given build_ids then use abrt-action-install-debuginfo. If you realy want to install it to abrt cache then please accept the fact that it's just a helper(wrapper) and run it from /usr/libexec.
Jirka
On 01/25/2012 03:12 AM, Jiri Moskovcak wrote:
On 01/20/2012 09:37 AM, Denys Vlasenko wrote:
On 01/19/2012 04:23 PM, Chris Meek wrote:
I little while ago I worked on a feature for systemtap where we could use abrt-action-install-debuginfo-to-abrt-cache to automatically download the required debuginfo to run a given script, by providing the build ID. I came across a couple bugs, specifically:
https://bugzilla.redhat.com/show_bug.cgi?id=730107 https://bugzilla.redhat.com/show_bug.cgi?id=726192
These appear to have been fixed, so I was planning on testing them out. I noticed, after upgrading to the most recent ABRT, that abrt-action-install-debuginfo-to-abrt-cache was moved to /usr/libexec/ from /usr/bin/.
I was just wondering if this should work the same way as before, or is it meant to be executed indirectly though something else in /usr/bin/ ?
I don't know why, but other guys on my team just LOVE moving stuff out of /usr/bin to less accessible directories. I think it's counter-productive, and you just provided a real life example why. Thanks! :)
/usr/libexec is for application which are not meant to be run from cmdline in usual cases. So it's not because we "LOVE to move stuf out from /usr/bin" we HATE polluting /usr/bin with executables which are used in 99.9% cases only as helpers.
Chris, abrt-action-install-debuginfo-to-abrt-cache is just a wrapper for abrt-action-install-debuginfo to make it run with SGID. If you just want to download the debuginfo packages for given build_ids then use abrt-action-install-debuginfo. If you realy want to install it to abrt cache then please accept the fact that it's just a helper(wrapper) and run it from /usr/libexec.
Jirka
Jirka,
Thanks for the clarification. I will look into using abrt-action-install-debuginfo instead.
Cheers, Chris
crash-catcher@lists.fedorahosted.org