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


Hi NoOp,

On Fri, 2011-04-22 at 20:13 -0700, NoOp wrote:
Just wanted to point out that both LO 3.4B1 & LO3.4B2 .deb installs
failed on my systems (miserably & yes, I'll go bug adding this weekend

        So - if you have a Linux system, and you're capable of installing
packages; then most likely you are able to climb the cliff of digging
around to work out how to package them for a different prefix -
right ? :-)

        So - please do try to fix the bug yourself, patches are most welcome.
If you come with some solid research, and some concrete suggestions / a
prototype patch you'll find some helpful feedback.

I find the response to Ed's post/comments/request on this list to be
'disturbing'.

        This is not a list for reporting random bugs on; of course Tor could
have just pointed him at bugzilla :-) but the reality is that we are
trying to do a lot of work, with very few resources and criticism is
hard to take under those circumstances. Concrete help is much more
appreciated. The "it is easy, you must be a moron" attitude is
-particularly- unhelpful.

        It is far better to do the bit of real work, study, research, code
reading, etc. yourself than write some long mail we all get to read
complaining about the lack of developer time to fix bugs ;-)

        HTH,

                Michael.

-- 
 michael.meeks@novell.com  <><, Pseudo Engineer, itinerant idiot


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.