thats looks good to me, I will take a closer look and see how it can be integrated.
Anas On 21 Jan 2011, at 20:06, Carsten Munk wrote: > 2011/1/19 Carsten Munk <[email protected]>: >> Hi, >> >> One of the biggest problems about debugging on mobile devices running >> MeeGo is that our debuginfo packages currently contain the entire >> source of the software. While this is nice for stepping through source >> code, it is horrible for simple backtraces that QA can use - as the >> needed debuginfo are too big for typical SD cards. Qt debuginfo as an >> example is -huge- to install :) >> >> openSUSE is having since 2008 debuginfo packages for the debug symbols >> and debugsources for the sources of the software in question on top of >> that, for those that want to step through code to debug deeper. >> >> Since this looks like a relatively straightforward patch, as seen at: >> >> https://build.opensuse.org/package/view_file?file=debugsource-package.diff&package=rpm&project=openSUSE%3AFactory&srcmd5=3b22d3db294c852fb824c0b11f49d51b >> >> Would it be accepted if I submitted a patch that added this >> functionality to our rpm (or the 4.9 work that is ongoing)? >> >> I personally think this could make our platform development a lot easier. > > I've implemented/adapted this from the openSUSE patches, patches added > at http://bugs.meego.com/show_bug.cgi?id=12724 - one patch for > meego-rpm-config, one for rpm. > > It was tested in devel:hardfp:base and as seen on > http://download.meego.com/live/devel:/hardfp:/base/standard/i686/ and > no ill effects seen (unless if you apply rpm before meego-rpm-config, > as there will be unpackaged files in debuginfo else) > > BR > Carsten Munk > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
