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

On Fri, Dec 10, 2010 at 1:37 PM, Carlos Jenkins <> wrote:
Hi Stefan,

2010/12/8 Stefan Weigel <>

I would never consider showing a selection of distros Debian,
Fedora, Mandriva, Mint, PCLinuxOS, Ubuntu, openSUSE rather than a
selection of package types Windows, Mac x86, Mac PPC, Linux x86 rpm,
Linux x86 deb, Linux 64 bit rpm, Linux 64 bit deb.

You have a good point. But I hope some day LibreOffice will be in a lot of
distros, we're aiming to become the default OfficeSuite for the mayor, if
not all, the Linux Distributions out there. Please check the Banshee website
and how the Download section behave:

I'm pretty sure his point was exactly the opposite of the banshee download page.

We need also, analyse the download widget from a user perspective, a list
box with options, if quick for people who know what to do,
it's absolutely not good for normal users.

I disagree. The vast majority of people in the world are indeed
capable of making a choice when presented with a simple question.

It's one thing to guide a user in making the appropriate and another
to make a choice for them.

I know, if you ask for Ubuntu a
lot users if they need to choose deb or rpm, they will not know, cause they
use Ubuntu Software Center to install things (and again my first point).

Sure that's why you try to "guide" to the DEB file.

Don't get me wrong though. I actually like the banshee download page.
It's the second step I don't like. The process gives me "instruction"
while I specifically came to the page to "Download" something.

And as Marc Paré stated nor they will know if 32bits or 64bits.

Seb said:
They are 3 possible answer DEB, RPM or Neither.

Yes, for now, we hope in the future we have instructions per distros like
the Banshee site. Also we need to jungle with +arch, +lang, +download
method, so it's a little more complex. But I think Samuel is on the right

No. There really are only 3 possibilities. Most popular distros use
RPM or DEB. And others use something specific to that distro in which
case the probably want the source anyway.

If you use a distro that uses deb or rpm you download the file, double
click on it, then the install starts. Simple. And everyone is familiar
with that. because that's how it's done on every major operating
system. Download, double click, install.

And for the those who don't have RPM or DEB. Well don't worry about
them because they know what they are doing. In fact the last thing
they probably want is a piece of Javascript telling them what to do.

As far as architectures go. The OO.o code is not exactly a success
story as far as ports go. I don't think we need to worry about that
just yet.

Language is trivial. I'm almost 100% sure that people know what
language they speak and can select it from a list. And keep it a list
because people often do install their office suite in a diffrent
language. For example I am a French speaking Canadian but I was born
in an bilingual part of Canada. As such I run most software in English
but my office suite in French.

Download method is also trivial. There can only be one.

In any case we have half of use that wants the distro thing and other
want the package thing. So lets compromise and do a bit of both.

See attached image.

PS: selecting other would add an extra step to choose between DEB, RPM
and Source.

Unsubscribe instructions: E-mail to
List archive:
*** All posts to this list are publicly archived for eternity ***


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.