From: Mikael Hallendal <hallski@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] openoffice ebuild (needs maintainer :-)
Date: 08 Dec 2001 02:51:53 +0100 [thread overview]
Message-ID: <1007776313.27951.10.camel@zoidberg> (raw)
In-Reply-To: <20011207150659.E9706@chiba.3jane.net>
[-- Attachment #1: Type: text/plain, Size: 862 bytes --]
fre 2001-12-07 klockan 22.06 skrev Daniel Robbins:
> On Fri, Dec 07, 2001 at 08:12:08AM +0100, Mikael Hallendal wrote:
> > Hi!
> >
> > Does anyone want to compile this or can't we just use the binary release
> > and put it in /opt?
>
> It sounds like this solution would be best for a majority of users. We can
> have two ebuilds (one sources and one binary).
Thats probably the best solution. I think that before any developer is
willing to spend a weekend getting this beast (and I used to think
Mozilla was a beast :) to compile we should add the binary-version so
that people can start using it.
>From what I've heard from my managers who use it the latest version was
a big step up speed-wise.
Regards,
Mikael Hallendal
--
Mikael Hallendal
Gentoo Linux Developer, Desktop Team Leader
CodeFactory AB, Stockholm, Sweden
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-12-08 1:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 20:47 [gentoo-dev] openoffice ebuild (needs maintainer :-) Dan Armak
2001-12-07 7:12 ` Mikael Hallendal
2001-12-07 7:48 ` Geert Bevin
2001-12-11 3:54 ` Dan Nelson
2001-12-11 15:44 ` Mikael Hallendal
2001-12-11 18:09 ` Zach Forrest
2001-12-12 0:46 ` Dan Nelson
2001-12-07 17:23 ` Joshua Pollak
2001-12-07 21:06 ` Daniel Robbins
2001-12-08 1:51 ` Mikael Hallendal [this message]
2001-12-08 5:51 ` Zach Forrest
2001-12-08 2:08 ` Taras
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=1007776313.27951.10.camel@zoidberg \
--to=hallski@gentoo.org \
--cc=gentoo-dev@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