Hi Michael, all,
Michael Meeks píše v Pá 29. 10. 2010 v 21:41 +0100:
The screwed up situation of having these two places to build, two
different conflicting makefiles with different rules etc. needs to be
cleared up ASAP - post the branch / freeze over the weekend, this
needs to be one of the first things we fix I think.
Indeed :-) So let me outline the plan here, so that people can scream
before I do that. [Actually, it was Petr's idea, so praise him if you
like it, but blame me if not :-)]
The idea is to forget the 'build' repository in the normal process, and
let it only for the documentation, and for the distro maintainers - if
they need it at all. 'bootstrap' would become the new main repo, and
would have the following layout:
/bootstrap
/autogen.sh
/configure.in
/dmake
...
/stlport # ie. the stuff it contains even now, plus
/clone # equivalent of build/clone we have now, containing
/artwork
/base
...
/writer
~accessibility
~afms
...
~zlib # links to the clone/*/[module], ie. equivalent of the
# content of rawbuild/
/bin # for scripts needed, namely 'g'
It will need some shuffling around, eg. the already mentioned 'g' script
(that will work both on 'bootstrap' itself, as well as on the repos in
clone/) will have to be moved from the build repo, or the ./download
script.
Also, we'll need to update bootstrap's configure.in to have the defaults
same as the current default LibreOffice{Linux,Win32,MacOSX}Devel distro.
Let me know if it works for you - hopefully yes :-)
Regards,
Kendy
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.