public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mark Knecht" <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] qt blockages...
Date: Mon, 19 Jan 2009 17:39:54 -0800	[thread overview]
Message-ID: <5bdc1c8b0901191739l708dfc39g8c97c90e3524a152@mail.gmail.com> (raw)
In-Reply-To: <497526A7.6090007@gmail.com>

On Mon, Jan 19, 2009 at 5:19 PM, Dale <rdalek1967@gmail.com> wrote:
<SNIP>
>
> 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 can understand that. I sort of operate that way. I think that there
really is a next step which is when you hit a problem like this take a
look at the Gentoo docs as well as write the list. I admit I often, or
even mostly, write the list first, but I think most of this stuff is
documented somewhere so it's a good thing to look at the docs also.
(At least once in awhile...) ;-)

>  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.

Gentoo is a hard distro to run on a slow speed interface. It's just
not set up for that.

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

Good luck and do find something faster. It will improve your
experience, I expect.

>
> Dale
>
> :-)  :-)
>
>



  reply	other threads:[~2009-01-20  1:39 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
2009-01-20  1:39               ` Mark Knecht [this message]
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=5bdc1c8b0901191739l708dfc39g8c97c90e3524a152@mail.gmail.com \
    --to=markknecht@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