public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: John White <johnjohn-gentoo-dev@triceratops.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] making %95 of users happy
Date: Fri, 19 Apr 2002 17:30:34 -0700	[thread overview]
Message-ID: <20020419173034.B4635@triceratops.com> (raw)
In-Reply-To: <20020419175758.32718.qmail@web13306.mail.yahoo.com>; from gaarde@yahoo.com on Fri, Apr 19, 2002 at 10:57:58AM -0700

On Fri, Apr 19, 2002 at 10:57:58AM -0700, Gaarde wrote:
> 
> DISCLAIMER:  I'm intentionally being rude... it helps convey my message.

Ah, how kind.
 
> Being so young, the documentation, the sence of community, the code (albeit
> in this case a 1.0 is quite nice.  Kudos guys!), everything about the Gentoo
> product is NOT AS MATURE AS MORE WIDELY DISTRIBUTED DISTRIBUTIONS!  What does
> 7.2 mean to you?  Or 8.1?  What does 1.1 mean to you?

Well, with people being intentionally rude, it seems like a nicely
developed and mature sense of community...
 
> I guess some people just jumped head first into Gentoo without knowing what
> they were getting into.  (The middle of a development cycle... that just
> never ends.)

Well, some people wait for a non < 1.0 release.  I know I did.

> Now, Consider the previous statement a direct *POKE* at the people I refer to
> as lusers.  Did they read the documentation?  

What?!?!?!  You just stated that the documentation isn't comparably
mature.  Actually, you stated that it wasn't comparably mature, and
that it's quite nice.  Or maybe it's just the code that's quite nice.
Perhaps you could clarify.  Or, being intentionally rude, perhaps you
won't.

> Did the read the part about profiles?  

In the comparably less mature documentation?  Are you talking about
the Portage Manual section 1, under Defaults, which talks about profiles
only in the context of default and auto USE variables (and not to change
make.defaults under make.profile/)?

Perhaps there's another profile documentation section which describes
how profiles should be used by the user to submit bug reports for
the current profile?  Not the Portage User Guid.  The word profile
doesn't exist there.

I think these kind of rants would be more effective with pointers
to the exact sections of documentation being referenced.  Because
as I enter my 7th day of reading gentoo docs, I'm not seeing them.

-- 
John White


  reply	other threads:[~2002-04-20  1:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-19 17:57 [gentoo-dev] making %95 of users happy Gaarde
2002-04-20  0:30 ` John White [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-20 18:26 Gaarde
2002-04-18 12:25 Gaarde
2002-04-18 18:29 ` Todd Wright
2002-04-18 19:28   ` Stefan Boresch
2002-04-19  3:25     ` Fuper
2002-04-19 12:04       ` Todd Wright
2002-04-18 22:09         ` Sherman Boyd
2002-04-19 14:15         ` Fuper
2002-04-18 19:35   ` Terje Kvernes
2002-04-19  8:42     ` Paul de Vrieze
2002-04-19  9:44       ` Terje Kvernes
2002-04-19 10:19         ` Einar Karttunen
2002-04-19 11:34           ` Mike Payson

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=20020419173034.B4635@triceratops.com \
    --to=johnjohn-gentoo-dev@triceratops.com \
    --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