Skip site navigation (1) Skip section navigation (2)

Re: Re: OpenOffice compile

From: Martín Marqués <martin(at)bugs(dot)unl(dot)edu(dot)ar>
To: "Craig Orsinger" <orsingerc(at)epg(dot)lewis(dot)army_mil(dot)invalid>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: OpenOffice compile
Date: 2001-05-28 08:07:10
Message-ID: 01052811071009.17025@bugs (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Mar 22 May 2001 22:57, you wrote:
> In article <200105221405(dot)f4ME5OG13140(at)candle(dot)pha(dot)pa(dot)us>, "Bruce Momjian"
> <pgman(at)candle(dot)pha(dot)pa(dot)us> wrote:
> > Off topic, but I thought this was interesting.  This is information
> > about compiling OpenOffice.  Hope PostgreSQL never gets to be this size:
> >
> >
> 	IMHO, basing an open project on 7.6M lines of code that can only
> compiled on four or five different architectures isn't a policy that
> anyone should emulate.

I think that the problem with OpenOffice is that it comes from StarOffice. 
Last time I downloaded SO was 5.2 and had over 70MB of binary, compressed. 
Anyway, I don't think you can get it smaller, but, as the people of 
OpenOffice are doing, you can always split it up, modularize it, so it is 
easy to make changes.

P.D.: Linux kernel hasquite an amount of lines of code, but the developers 
have no problem finding bugs and all the stuff.

Saludos.... :-)

Cualquiera administra un NT.
Ese es el problema, que cualquiera administre.
Martin Marques                  |        mmarques(at)unl(dot)edu(dot)ar
Programador, Administrador      |       Centro de Telematica
                       Universidad Nacional
                            del Litoral

In response to

pgsql-hackers by date

Next:From: Hannu KrosingDate: 2001-05-28 09:11:46
Subject: Re: AW: Plans for solving the VACUUM problem
Previous:From: Zeugswetter Andreas SBDate: 2001-05-28 08:02:17
Subject: AW: Plans for solving the VACUUM problem

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group