public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Beso <givemesugarr@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64]
Date: Fri, 6 Jul 2007 19:56:56 +0200	[thread overview]
Message-ID: <d257c3560707061056n48a185a2h588df3788615e58d@mail.gmail.com> (raw)
In-Reply-To: <20070706152051.GA25052@v.igoro.us>

[-- Attachment #1: Type: text/plain, Size: 3139 bytes --]

2007/7/6, Dustin J. Mitchell <dustin@v.igoro.us>:
>
> On Fri, Jul 06, 2007 at 09:02:05AM -0400, B. Nice wrote:
> > > I also feel a little guilty that my only contribution as an AT is to
> > > make fun of people trying to unsubscribe from the list.  It's not
> > > exactly productive, and only serves to reinforce the bad rep that
> Gentoo
> > > has.
> > Where do people get the idea that Gentoo has a bad reputation?  I've
>
> Well, keep in mind that I run in what is probably a slightly different
> circle -- server admins.
>
> Gentoo has a *lot* to recommend it technically for administering a
> server -- fine-grained control, careful management of the upgrade path,
> transparency, extensibility, etc.
>
> But the cultural shift is painful when folks like me try to interact
> with the Gentoo user or developer community.  I think I'm a fairly
> technically adept person (hey, I passed the ebuild quiz), yet several of
> my bugs have been blown off fairly rudely, by developers who had
> obviously not read the entire bug.  Of course, interactions on IRC are
> even worse.


this is the thing that i hate.... if you get a bug you should test if it
will come when you have the entire system from the stable branch and see if
it happens also there....

The result is that I don't file bugs anymore -- I make a fixed local
> copy of the ebuild and call it a day.  Since I can't recommend that my
> clients and employers do the same, I set them up with a RedHat-derived
> base system and then hand-compile the necessary software on top of that.
>
> By way of comparison, problems I have had with specific pieces of
> business-critical software (vs. with the distro) have been handled with
> professionalism and dignity.
>
> Maybe the problem is that Gentoo devs are *too* accessible, and aren't
> really given a choice in the matter.  Does e.g.,
> https://bugzilla.novell.com/ see the same level of activity as Gentoo's?
> I imagine that a lot of the grumpy devs would probably do well just
> sitting in the background and coding.


the novell bugzilla has not very much activity because the commercial
version has paid support and because novell commercial systems are pretty
good in terms of bugs.... ok, they are a little backward with the software
versioning, but their commercial versions are really great pieces of
stability.... for what i have experienced by using for quite some time suse
and opensuse lately, that distribution is the best fast install and use
linux distro existing.... and then there is gentoo that is very good for
tuning your pc.... all the others that i've tryied (from fedora, to
archlinux, to ubuntu, kubuntu, debian and others) suck!!!! if you want a
quick install linux distro with great support and lot of features get
opensuse, and if you want a great personal machine optimized linux distro
get gentoo or sabayon (the last one i'll have to try it out)....

Those are my musings..
>
> Dustin
>
> P.S. I should add that the amd64 group does not seem to share these
> difficutlies -- this list is sometimes irreverent, but never insulting.
> --
> gentoo-amd64@gentoo.org mailing list
>
>


-- 
beso

d-_-b

[-- Attachment #2: Type: text/html, Size: 3996 bytes --]

  parent reply	other threads:[~2007-07-06 18:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-06  2:02 [gentoo-amd64] Joshua Hoblitt
2007-07-06  2:25 ` [gentoo-amd64] Dustin J. Mitchell
2007-07-06 13:02   ` [gentoo-amd64] B. Nice
2007-07-06 15:20     ` [gentoo-amd64] Dustin J. Mitchell
2007-07-06 17:51       ` [gentoo-amd64] Duncan
2007-07-06 18:17         ` Beso
2007-07-06 17:56       ` Beso [this message]
2007-07-09  2:24       ` [gentoo-amd64] Gavin Seddon
2007-07-10  9:07         ` [gentoo-amd64] Duncan
     [not found] <20081123120010.F2CB5E05BE@pigeon.gentoo.org>
2008-11-23 12:30 ` [gentoo-amd64] David Burkinshaw
  -- strict thread matches above, loose matches on Subject: below --
2005-11-15 22:27 [gentoo-amd64] Janus Rasmussen
2005-08-12  3:07 [gentoo-amd64] Ben
2005-08-12 10:45 ` [gentoo-amd64] Simon Stelling
2005-08-12 12:38   ` [gentoo-amd64] Drew Kirkpatrick
2005-08-12 19:19     ` [gentoo-amd64] phil
2005-08-12 22:11       ` [gentoo-amd64] Dice R. Random
2005-08-12 22:48         ` [gentoo-amd64] felix
2005-08-12  0:15 [gentoo-amd64] Ben
2005-08-12  8:47 ` [gentoo-amd64] Simon Stelling

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=d257c3560707061056n48a185a2h588df3788615e58d@mail.gmail.com \
    --to=givemesugarr@gmail.com \
    --cc=gentoo-amd64@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