Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


I'll bring this up at our next conference call and see if there is a
possible solution.


Best Regards,
Joel

On Fri, Sep 7, 2012 at 12:48 PM, John Smith <lbalbalba@gmail.com> wrote:

On Fri, Sep 7, 2012 at 9:42 PM, Joel Madero <jmadero.dev@gmail.com> wrote:


Sounds good, but I agree with John that better instructions are needed.
I'm
working on a new triage page and hopefully in there we can get someone to
contribute incredibly precise, easy for noobs, instructions for every
type
of backtrace/debug. Right now they are really written by experts for
experts
(IMO). I would backtrace much more frequently if I could follow the
instructions on how to do it. Every time I feel like I have to go on IRC
and
ask 100 questions.






I don't think we have enough people packaging to make pre-built binaries
for
everyone. Plus, these are huge, my install is 22 gigs with all symbols
on,
not very good for packaging purposes.

I guess it all depends on who your target audience is. If you really
want end-users (libre office users) to provide backtraces, you really
need to make the threshold for doing that as low as possible. I dont
think it is reasonable to have end-users compile source code for
themselves; especially on windows, where it requires msvc or cygwin to
do so.


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.