From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] LibreOffice 3.4.4: required HDD space
Date: Sun, 20 Nov 2011 14:07:51 -0500 [thread overview]
Message-ID: <CA+czFiAh7TSqu61hciiyGQLKjemTqD=qkN96ETmizrJGL8K-bw@mail.gmail.com> (raw)
In-Reply-To: <CA+hid6F6JcfzJ9SsjtdeotZYSd2rYySdr47ZorJAsSFYeLd1KA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
On Nov 20, 2011 2:04 PM, "James Broadhead" <jamesbroadhead@gmail.com> wrote:
>
> On 20 November 2011 18:32, Neil Bothwick <neil@digimed.co.uk> wrote:
>>
>> On Sun, 20 Nov 2011 09:07:33 -0500, Michael Mol wrote:
>>
>> > Ok, then I'll narrow my guess to the size required being dependent on
>> > USE flag combinations.
>>
>> Also CFLAGS and architecture, to a lesser extent.
>
>
> Seeing as the ebuild is 'aware' of CFLAGS and USE, it would be nice if it
would use that information (roughly) to determine how much space to check
for.
>
> 4-9GiB is a pretty wide range.
Imractical; you'd have a count of possible sizes increase geometrically
with the number of USE flags, and it's not going to be something so simple
as "this adds N MB, this adds M MB..."
[-- Attachment #2: Type: text/html, Size: 1057 bytes --]
next prev parent reply other threads:[~2011-11-20 19:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-20 9:09 [gentoo-user] LibreOffice 3.4.4: required HDD space v_2e
2011-11-20 11:12 ` Philip Webb
2011-11-20 11:52 ` Volker Armin Hemmann
2011-11-20 14:43 ` smalker
2011-11-20 14:07 ` Michael Mol
2011-11-20 18:32 ` Neil Bothwick
2011-11-20 18:58 ` James Broadhead
2011-11-20 19:07 ` Michael Mol [this message]
2011-11-20 19:30 ` Dale
2011-11-20 20:09 ` Alan McKinnon
2011-11-26 13:49 ` James Broadhead
2011-11-26 14:10 ` Alan McKinnon
2011-11-27 1:06 ` Dale
2011-11-27 16:07 ` [gentoo-user] " Grant Edwards
2011-11-20 19:07 ` [gentoo-user] " v_2e
2011-11-20 19:18 ` Michael Mol
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='CA+czFiAh7TSqu61hciiyGQLKjemTqD=qkN96ETmizrJGL8K-bw@mail.gmail.com' \
--to=mikemol@gmail.com \
--cc=gentoo-user@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