public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] qt blockages...
Date: Mon, 19 Jan 2009 19:19:35 -0600	[thread overview]
Message-ID: <497526A7.6090007@gmail.com> (raw)
In-Reply-To: <5bdc1c8b0901191631h2577f67cge7976962fd754e6a@mail.gmail.com>

Mark Knecht wrote:
> On Mon, Jan 19, 2009 at 4:18 PM, Dale <rdalek1967@gmail.com> wrote:
> <SNIP>
>   
>> Hence the question, should this be a default option?  I'm not the only
>> one that has ran into this.
>>
>> Dale
>>     
>
> Maybe it's a forest for trees thing but it's in the man page and shows
> up early in Gentoo Portage documentation:
>
> http://www.gentoo.org/proj/en/portage/doc/faq.xml
>
> I don't think it's required for all folks so I don't think it should
> be default. It does result in longer emerge cycles as it grabs and
> builds more code on average. Many folks might not want that.
>
> Just my thoughts,
> Mark
>
>
>   

It's sort of funny in a way.  I hardly ever go to the Gentoo website.  I
follow this list and -dev and learn that way.  I sync usually each
Friday or Saturday and usually by the time I get the packages downloaded
over my slow dial-up, if there are any problems with something it will
be on the list by then.  I do on occasion search the forums.  I'm going
through the qt blockages now but I still have a lot to download yet. 
That qt-core package is huge.  Almost like OOo.  Then there are the
brothers, sisters and children of that thing to go with it. 

I need broadband something awful.  I don't think sticking a stick of
dynamite under AT&T would do any good at all either

Dale

:-)  :-) 



  reply	other threads:[~2009-01-20  1:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-18 22:26 [gentoo-user] qt blockages Mark Knecht
2009-01-18 22:54 ` Christopher Walters
2009-01-18 23:47   ` Mark Knecht
2009-01-19 10:31     ` Mick
2009-01-19 11:58       ` Dave Jones
2009-01-19 12:53         ` Markos Chandras
2009-01-20 11:46         ` Mick
2009-01-19 22:18 ` KH
2009-01-19 22:37   ` Mark Knecht
2009-01-19 23:13     ` Dale
2009-01-20  0:03       ` Paul Hartman
2009-01-20  0:18         ` Dale
2009-01-20  0:31           ` Mark Knecht
2009-01-20  1:19             ` Dale [this message]
2009-01-20  1:39               ` Mark Knecht
2009-01-20  0:46           ` Neil Bothwick
2009-01-20  1:36     ` Nickolas Fortino
2009-01-20  8:47       ` Neil Bothwick
2009-01-20  8:01   ` Daniel Pielmeier
2009-01-20  8:11     ` KH
2009-01-20  8:40       ` Daniel Pielmeier
2009-01-20  8:53       ` Nickolas Fortino
2009-01-20  9:12         ` KH

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=497526A7.6090007@gmail.com \
    --to=rdalek1967@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