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


On Thu, Oct 29, 2015 at 6:32 PM, jan iversen <jancasacondor@gmail.com> wrote:



Thanks for the answer, I will make a copy of that repo (so much for "core is
the only repo you will ever need")

if you downloaded and used that ps1 file, that indicate that you were
following the 'lode' ways of setting up a build environment (a good
thing.. but I'm partial :-) ).
step 2 of this process _is_ to download the lode.git repo.. so you
should really already have it.

And yes core.git is all you need to build the product ( although
depending on the build option you may get dictionaries.git, help.git
and/or translation.git as git submodule).
lode.git is a separate 'tools' developed originally to help deploying
ci slavebot.
lode help among other thing 'manage' core.git using a local bare
mirror clone --reference to deply build environment cheaply.
it could not live in core.git again due to a chicken and egg problem.

and as you can see here: https://gerrit.libreoffice.org/#/admin/projects/

we do have quite a few auxiliary git repo under management :-)

I was told (on irc) by mst that our web server content is not in git (which in my mind seems wrong)

most of it is not, for good reason.. git is not the best way to manage
a bunch of fat tar.gz source release of all the external dependencies
we use.
I've put that particular script _there_ as a convenience (convenient
to me as that web server already existed and server plain file), but
really the cygwin_install scrip is completely unrelated to the rest of
the content there.

Norbert

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.