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


Hi Nicholas, *,

On Wed, Oct 1, 2014 at 2:50 PM, nicholas ferguson
<nicholasferguson@wingarch.com> wrote:
[...]
Where is it mentioned how not to keep downloading the tar files? for
3rd party dependencies.  That alone is a HUGE COST OF ENTRY...to
discover how to turn that off.

     The automatic download saves manually downloading 70 or so individual dependencies; you 
can argue that it sucks (and it does) - but doing that manually sucks more =)

The high cost of entry only comes because you just didn't follow the
instructions on setting up a windows build system.
https://wiki.documentfoundation.org/Development/Windows_Build_Dependencies

Yes, you need to install some stuff. But all you have to do is to read
and copy'n'paste the commands.

A build for a newcomer has to be run three or four times?  Why should the tar files get 
downloaded four times?  How does a newcomer turn it off after the first download?

The page suggests default parameters, amogst them is:
--with-external-tar=/cygdrive/c/sources/lo-externalsrc

And also: If you just go wild and delete everything from your sources
again and again, then even when not using a separate directory, the
files would not be redownloaded over and over.

Don't blame the buildsystem or the documentation when you deliberately
chose to do your own thing/actively work against it.

ciao
Christian

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.