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


 On 08/10/10 02:32 PM, RGB ES wrote:
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 ;) )
And that's why I was asking about whether it was possible to have repositories on the documentfoundation.org servers. Users of Debian (and its derivatives) could put "apt.documentfoundation.org" into their sources.list file and there would be a one-stop shop for that distribution to put LibO into users hands. I'm assuming rpm's and other distribution packaging could be setup in a similar fashion. In the same light, Windows users would have a download source for updates.

Would this be a security headache?
Could this work for the average user?
Does this not seem a convenience for the end-user community at large?

Others could mirror this repository, but this would be the "upstream source" for both users/distributions.
Are there other factors I'm missing?

Regards,
Scott Furry
--
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.