public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] What happens with masked packages?
Date: Mon, 27 Feb 2006 18:51:29 +0000	[thread overview]
Message-ID: <20060227185129.3321b078@snowdrop.home> (raw)
In-Reply-To: <440337FA.6070800@joat.com>

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

On Mon, 27 Feb 2006 12:33:46 -0500 Dave Nebinger <dnebinger@joat.com>
wrote:
| Your statement is probably true for all of the binary distribution 
| folks.  But I doubt that you'll get many from this crowd that would
| say that we want or expect the gentoo team to "know what's best for
| [us]."

What, you think that everyone here knows exactly which version of gcc,
with which patches and which corresponding binutils to use? You think
that everyone here knows exactly which versions of db they do and do
not need installed? You think that everyone here knows which kernel
headers they should be using and in what way they should be patched?

Most of our users don't have a clue about those questions. Heck, most
of our devs don't either. Figuring all that stuff out correctly is a
hell of a lot of work. One of the major reasons for using Gentoo over
LFS is that someone else has done said work for you.

-- 
Ciaran McCreesh : Gentoo Developer (Wearer of the shiny hat)
Mail            : ciaranm at gentoo.org
Web             : http://dev.gentoo.org/~ciaranm


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 191 bytes --]

  reply	other threads:[~2006-02-27 19:05 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-22 19:55 [gentoo-user] What happens with masked packages? Thierry de Coulon
2006-02-22 20:02 ` Dave Nebinger
2006-02-22 20:38   ` Thierry de Coulon
2006-02-22 21:38     ` Rafael Bugajewski
2006-02-22 22:12     ` Boyd Stephen Smith Jr.
2006-02-22 22:44       ` Dave Nebinger
2006-02-22 22:53       ` Thierry de Coulon
2006-02-22 23:08         ` Boyd Stephen Smith Jr.
2006-02-24 17:31       ` Ciaran McCreesh
2006-02-24 20:57         ` Boyd Stephen Smith Jr.
2006-02-25 18:57           ` Ciaran McCreesh
2006-02-25 19:34             ` Boyd Stephen Smith Jr.
2006-02-25 23:47               ` Mariusz Pękala
2006-02-26  5:16                 ` Boyd Stephen Smith Jr.
2006-02-26 16:34                   ` Mariusz Pękala
2006-02-26 17:06                   ` Bo Andresen
2006-02-26 20:40                     ` Boyd Stephen Smith Jr.
2006-02-26 23:25                       ` John J. Foster
2006-02-27  0:15                       ` Bo Andresen
2006-02-27  0:57                         ` Boyd Stephen Smith Jr.
2006-02-27  3:44                           ` Zac Slade
2006-02-26 16:11               ` Ciaran McCreesh
2006-02-26 23:29                 ` John J. Foster
2006-02-27  0:11                   ` Ciaran McCreesh
2006-02-27  1:26                     ` John J. Foster
2006-02-27 17:17                       ` Ciaran McCreesh
2006-02-27 17:33                         ` Dave Nebinger
2006-02-27 18:51                           ` Ciaran McCreesh [this message]
2006-02-22 21:27 ` Boyd Stephen Smith Jr.

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=20060227185129.3321b078@snowdrop.home \
    --to=ciaranm@gentoo.org \
    --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