Re: [tdf-discuss] A better idea for a download package.
----- Original Message ----
From: Charles Marcus <CMarcus@Media-Brokers.com>
On 2010-11-30 2:16 PM, Kevin Vermeer wrote:
Perhaps the installer could be replaced by a small configuration
application, which would allow the user to select the components they wish
to install, and would then download the selected components?
This is fast becoming an FAQ...
LibO - like OOo - does not really have separate components. Even if you
could download just one component, the resulting size would only be a
few MBs smaller than it is now.
While that may currently be the case - that is absolutely ridiculous.
TDF/LO should make a priority of resolving that issue.
Componentizing it is such a huge job that it is really not worth
It will most certainly be worth it as things will get easier to maintain
It will also allow for better installation flexibility.
It also has nothing to do with the software being seamlessly integrated. I
understand that StarOffice was once one big integrated application - I used
SO5/6 at one point under the free license before OOo exited. However, that
doesn't mean that everything needs to depend on everything else. Having such a
complex code structure will simply push developers away - yes, I did look at
modifying OOo at one point (a few years ago), only I was unable to figure out
where to even start due to code structure and organization. (I do hope to try
again at some point when I get the chance.)
Having created installers before - namely MSI's - there should ultimately be no
reason why the installer should be broken down as:
- core LO libraries used by each package
- package for each app (writer, calc, etc.)
- separate language packages for documentation and language bindings
- extensions & clip art can be added as additional packages of varying sizes
(e.g. most popular, top 100, etc.)
In MSI terms each of the above would be an MSI Merge Module, with each installer
just being a conglomerate of Merge Modules for all the pieces
and the necessary glue.
Many open source projects - TortoiseSVN, Pidgin IM, Gtk, KDE SC, to name a few -
already do this kind of thing too; and commercial software highly utilizes such
mechanisms to tailor installs to different customer groups.
KDE on Windows (windows.kde.org) even provides an installer that downloads over
the Internet the required parts for the install - not saying that's how we
should go about. But you definitely need to target things a bit differently to
capture more people groups - in terms of language, and network connectivity. As
an organization, TDF should look at selling USB sticks, CDs, and DVDs on-line
for those without Internet or extremely slow downloads - a good way to raise
some money to support the organization with too. (Yeah, volume probably won't be
very high; though if planned out well, it could even be put into on-line and
brick & mortar stores too - though I'd just offer on-line to start and provide a
contact page for distributors that want to carry it.)
A LO/Writer installer should just be the necessary parts for LO/Writer. Same for
an LO/Calc installer.
Documentation and additional language packages could be supplemental downloads.
The current size problem as compared to OOo is because all of the
language packs are included... and this situation is only temporary
until storage is no longer an issue...
Patience, I'll agree - but a real solution is necessary.
Unsubscribe instructions: E-mail to email@example.com
*** All posts to this list are publicly archived for eternity ***
Impressum (Legal Info)
: 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