Gentoo Logo
Gentoo Spaceship

Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-pms
Lists: gentoo-pms: < Prev By Thread Next > < Prev By Date Next >
To: Brian Harring <ferringb@...>
From: Ciaran McCreesh <ciaran.mccreesh@...>
Subject: Re: kdebuild-1 conditionals
Date: Fri, 11 Dec 2009 18:20:32 +0000
On Fri, 11 Dec 2009 08:59:14 -0800
Brian Harring <ferringb@...> wrote:
> One potential compromise- tag in a section in pms about "nonstandard 
> eapis" and throw in some links to places folks can look.  That
> general approach should provide a way to retire standardized EAPIs
> from the doc also- same thing "go look here".

Why bother? That's quite a bit of work. Instead, what's wrong with a
gradual, carefully controlled phasing out?

The first step (preventing people from installing any more kdebuild-1
things) was already done recently, when the genkdesvn repo was removed.

The second step (ensuring that people no longer have kdebuild-1
packages installed) can be done with the next major Paludis release.

The third step (removing it from everywhere) can be left until after
we've given everyone reasonable time to clean up.

Doing things that way has little to no cost and little to no user
impact, whereas rushing to remove kdebuild-1 without thought for the
effects reeks of "huh huh, let's try to wind people up".

Ciaran McCreesh
signature.asc (PGP signature)
Re: kdebuild-1 conditionals
-- Ulrich Mueller
kdebuild-1 conditionals
-- Christian Faulhammer
Re: kdebuild-1 conditionals
-- Brian Harring
Lists: gentoo-pms: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: kdebuild-1 conditionals
Next by thread:
Re: kdebuild-1 conditionals
Previous by date:
Re: kdebuild-1 conditionales
Next by date:
Re: Re: kdebuild-1 conditionals

Updated Jul 18, 2012

Summary: Archive of the gentoo-pms mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.