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


On 10/06/2010 11:06 AM, Charles Marcus wrote:
On 2010-10-06 1:04 AM, Scott Furry wrote:
Any installation method that is deployed, in my mind, must 'respect'
the package management of the base operating system.

+1 - So, for most *nix's, this would mean that the built-in LibO updater
should be disabled, and let the systems package manager take care of it.

Yes, I think so.  For a yum/RPM system, for example, it would be nice if
the initial install of LibO was accomplished by having the user
configure a yum repository (which is simple and short), not by
downloading a huge installation file manually.  Automating this kind of
yum configuration is possible with an RPM.  I.e., the developers create
an RPM that does nothing but configure the user's yum repos, and expose
that RPM to the users via the website.  Then installations and updates
can be as simple as

# yum install libreoffice

and

# yum update libreoffice

The yum package manager would then be able to handle dependencies,
resuming downloads after a broken connection, etc., in a robust way.
Then we wouldn't have to use a ./setup script that bypasses the package
manager, or manually install a desktop menus RPM.

     ----Jon
-- 
To unsubscribe, send an empty 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.