iHi,
On Fri, Dec 21, 2012 at 06:57:53AM +0000, Michael Meeks wrote:
Ho hum; the Raspberry Pi version is mostly Rene's work with the Debian
packages; I'd stick to just having the Linux + ARM architecture for that
rather than a specific one (unless you really think it helps).
I agree wth that. Debian ARM or Raspbian or whatever pi store thing is imho
simply "Linux/ARM". Whether upstream ships binaries for those doesn't really
matter for bugzila imho, the port is upstream and thus if there's
a arch-dependant bug there it's (most times) a uüstream one. And if the bug is
not arch-specific it is anyway.
See http://packages.debian.org/search?keywords=libreoffice-core for what
architectures we provide packages for (alpha is dead upstream, though
...
Android is a different matter of course; unclear what to do there - at
least, that stuff is quite experimental except for the impress remote
which should be toughened up enough to ship in 4.0. So whatever you
think really ...
I _personally_ think we should add something to bugzilla only if
we have _somthing_ working (alpha? beta?) for the pubnlic, not earlier...
Regards,
Rene
--
Unsubscribe instructions: E-mail to marketing+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/marketing/
All messages sent to this list will be publicly archived and cannot be deleted
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.