public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Boyd Stephen Smith Jr." <bss03@volumehost.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] OpenOffice.org natively available for AMD64
Date: Mon, 16 Oct 2006 08:23:40 -0500	[thread overview]
Message-ID: <200610160823.40596.bss03@volumehost.net> (raw)
In-Reply-To: <29c147bd0610160603g34a34cd7q3a7a9e0731eb9130@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]

On Monday 16 October 2006 08:03, "Lorenzo Milesi" 
<lorenzo.milesi@gmail.com> wrote about 'Re: [gentoo-amd64] OpenOffice.org 
natively available for AMD64':
> > It finally happened: openoffice is expected to compile and work
> > natively on amd64.
> I had seen it this morning, and I though "What?!" :)
> Which are the real advantages in compiling OOo instead of using -bin?

Well, it certainly looks and feels different when compiled with the kde 
useflag, or at least did on my x86 laptop.

Also, the version I compiled on my memory-starved 2.4GHz P4 laptop started 
5-10 times faster then the binary version installed on my 2.2GHz 4GB RAM 
2x Dual-core Opteron monster.

OOo-bin sucked so much on AMD64 (for me, it's subjective) that I loved it 
when KOffice finally became usable for me.

-- 
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-10-16 13:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-16 11:30 [gentoo-amd64] OpenOffice.org natively available for AMD64 Simon Stelling
2006-10-16 12:12 ` Sebastian Redl
2006-10-16 13:03 ` Lorenzo Milesi
2006-10-16 13:23   ` Boyd Stephen Smith Jr. [this message]
2006-10-16 13:29   ` Michael Weyershäuser
2006-10-16 13:30   ` Christoph Mende
2006-10-18 16:28     ` Felipe Ribeiro
2006-10-18 18:14       ` Jean-Marc Hengen
2006-10-19  3:08         ` Vladimir G. Ivanovic
2006-10-19  3:23           ` Gary E. Miller
2006-10-19  3:31             ` Vladimir G. Ivanovic
2006-10-19  3:29           ` Vladimir G. Ivanovic
2006-10-19  4:38             ` Neil Cathey
2006-10-19  4:42               ` Neil Cathey
2006-10-19 16:08                 ` Vladimir G. Ivanovic
2006-10-19 18:10                   ` Neil Cathey
2006-10-16 13:19 ` Boyd Stephen Smith Jr.
2006-10-18 15:41 ` Juergen Schinker
2006-10-23 15:41 ` Peter Humphrey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200610160823.40596.bss03@volumehost.net \
    --to=bss03@volumehost.net \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox