public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Francesco Riosa <francesco@pnpitalia.it>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] USE & KEYWORDS relation
Date: Wed, 02 Mar 2005 22:30:23 +0100	[thread overview]
Message-ID: <4226306F.2050403@pnpitalia.it> (raw)
In-Reply-To: <1109794265.9520.107.camel@cgianelloni.nuvox.net>

Chris Gianelloni ha scritto:

>On Wed, 2005-03-02 at 20:47 +0100, Francesco Riosa wrote:
>  
>
>>bob already know how to downgrade but he can't because his boss has 
>>crashed its chair on his head and now he his at the hospital.
>>bad boss, bad world
>>    
>>
>
>In your scenario, Bob is an Admin.  If Bob were *my* admin and had not
>taken the time to read the ChangeLog for the package and not made
>changes on the test network before making them to the production
>network, Bob would be looking for a new job after that coffee.  Also, if
>Bob were not smart enough to not stay with the stable portion of Gentoo,
>which is designed to not have feature loss and other such problems, but
>was instead using the "testing" branch on production servers, then Bob
>would be looking for a new job and I would be looking for a smarter
>administrator.
>
>The whole point is that if you are blindly upgrading *anything* that you
>rely on for day-to-day work, that really there is only one person to
>blame, and that is yourself.
>  
>
Chris,
  Really we are not speaking about me, I blindly make all kind of crappy 
stuff but _**never**_ on production system. Seldom on backup of 
production systems. I like the risk but not when it compromise other 
person than me.

*The* whole points are
that there is no way of choose  a  set  of  features  (via USE flag) and 
expect that emerge keep updated my system obeying to my needs.
the stable/unstable stuff it's *not* a point what happen if upstream of 
say "l7" goes away for six month? your latest stable version will *stop* 
for six month.
Maybe iptables-1.3 must become stable before, and *ONLY* the people who 
want "l7" must stop at 1.2.9
* this * is * the * point *

Now you can say that it's easy or not, possible or impossible, you can 
ever say do it yourself (but expect that I do it).
What you can*not* say is that is a stable/unstable problem, or that the 
user must check before the user *will* check before he/she should not be 
costrained to mess with its /etc/portage/package.mask for *this* kind of 
stuff.

my apologies if that was not clear before, hoping that now it's better 
explained


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2005-03-02 21:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-02 14:48 [gentoo-dev] USE & KEYWORDS relation Francesco Riosa
2005-03-02 15:02 ` Simon Stelling
2005-03-02 15:17   ` Francesco Riosa
2005-03-02 18:37     ` Henrik Brix Andersen
2005-03-02 18:46       ` Mike Frysinger
2005-03-02 18:54         ` Francesco Riosa
2005-03-02 15:18   ` Daniel Gryniewicz
2005-03-02 18:07     ` Colin Kingsley
2005-03-02 18:41       ` Francesco Riosa
2005-03-02 19:34         ` Mike Frysinger
2005-03-02 19:47           ` Francesco Riosa
2005-03-02 20:11             ` Chris Gianelloni
2005-03-02 21:30               ` Francesco Riosa [this message]
2005-03-02 19:37         ` Simon Stelling
2005-03-02 19:44           ` Francesco Riosa
2005-03-03  5:35         ` Colin Kingsley
2005-03-03  9:16           ` Francesco Riosa

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=4226306F.2050403@pnpitalia.it \
    --to=francesco@pnpitalia.it \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-dev@robin.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