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


2010/10/8 Marc Paré <marc@marcpare.com>:
Do you know what the reasons were for not using these? It would seem to m
ake
sense that you would want to free up dev work and try to unify an upgrade
process for everyone.

Because at the end of the day, they do not work. Just one word:
dependencies. If you try to install as user something that needs
shared libraries the probability you end with a mess is high:
duplicated libraries is just one of the problems, track what is on
your system (and clean what is not needed any more) is another.
Just look at what happens on windows, with the miracle of the
multiplying libraries: windows systems tends to get "fatter" (and
slower, and...) with time just because the install/upgrade system for
apps is not centralized.
Software repositories managed by system applications (yum, libzipp...
whatever) ARE an unified upgrade system, reliable, secure and fast
that simplify your life. You just need online storage capacity and
someone who build the packages, but that someone do not need to be a
developer: almost anyone can build packages (after a period of
training, of course ;) )
--
To unsubscribe, e-mail to discuss+unsubscribe@documentfoundation.org
All messages you send to this list will be publicly archived and cannot be deleted.
List archives are available at http://www.documentfoundation.org/lists/discuss/

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.