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


[ Sorry, replied off-list unintentionally. ]

On Sat, Jul 23, 2011 at 04:10:37AM +0200, Bjoern Michaelsen <bjoern.michaelsen@canonical.com> wrote:
I have reverted the gbuildization of gnumake4 in writerfilter and kept
"our" gbuildization. Still I think, we(**) should take a very close look
at that, as it seems to be doing some things quite right. I got the
gnumake4 gbuildization working, but I did not resync that state with the
latest changes in writerfilter. I created two temporary tags in filters:
-
http://cgit.freedesktop.org/libreoffice/filters/tag/?id=feature/gnumake4_writerfilter_base
- 
http://cgit.freedesktop.org/libreoffice/filters/tag/?id=feature/gnumake4_writerfilter_head

which are the working gnumake4 gbuildization state (head) and "our"
master state it was based on (base). That diff (in writerfilter only) is
pushed as a featurebranch:
 http://cgit.freedesktop.org/libreoffice/filters/commit/?h=feature/gnumake4_writerfilter

which we can merge to master, if we choose to. Otherwise, we should
delete those.

Hi Bjoern,

As we discussed on IRC in the long term it's a good idea to do what is
in gnumake4 (merge the various small libs to a single writerfilter lib);
but probably it makes more sense to do it once rtftok is not under heavy
development. Of course if you / David want to do it right now I can live
with that as well.

Thanks.

Attachment: pgpTx8G0liEHt.pgp
Description: PGP signature


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.