RE: [Evolution] huge RPMs

[Joe Shaw <joe helixcode com>]

> > > Probably because the executables aren't stripped of debugging
> > > information.  This helps by making it possible to provide useful
> > > debugging information when evolution crashes, at the expense of a bit
> >
> > But if I make rpms myself (with rpm -tb command) they are much
> > smaller. It is nonsense - user who compiles himself may not
> > want to strip libraries, the end user who downloads only rpms
> > gets unstripped ones. And I don't think users who download
> > binary rpms know how to use gdb.

Most users who download binary RPMs -do- know how to use bug-buddy, which
uses gdb to get stack traces. With an application that is as complex as
Evolution, if the developer can't reproduce the problem from a report, a
bug report without a stack trace is nearly useless.

We provide our RPMs unstripped because it makes out lives easier; it
allows us to track down bugs more quickly and reduces development
time. The other option is to download and build from source. I'm sorry you
have to pay by the minute, but this isn't going to change before 1.0; it
just doesn't make sense.

Joe