public inbox for gentoo-pms@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: Brian Harring <ferringb@gmail.com>,
	Christian Faulhammer <fauli@gentoo.org>,
	gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] kdebuild-1 conditionals
Date: Fri, 11 Dec 2009 21:58:31 +0000	[thread overview]
Message-ID: <20091211215831.09244f04@snowmobile> (raw)
In-Reply-To: <19234.48824.521170.185497@a1i15.kph.uni-mainz.de>

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

On Fri, 11 Dec 2009 22:50:48 +0100
Ulrich Mueller <ulm@gentoo.org> wrote:
> >>>>> On Fri, 11 Dec 2009, Ciaran McCreesh wrote:
> 
> > I need it there for as long as there is support for it in Paludis,
> > which is two major releases away if we do this the responsible way
> 
> So keep an old version of it around for your own personal use. Where's
> the problem with this?

There are better mechanisms available, and they have zero cost since
they've already been implemented.

> > What's wrong with leaving something that's already there in place
> > for a while longer?
> 
> It makes the LaTeX source almost unreadable in some places, and
> therefore makes working with it more difficult.

Then ask the Council for permission to turn it on unconditionally.

Having said that, the people who have done the majority of the most
recent changes haven't had any particular difficulty with the
conditionals.

> And please specify what timeframe you mean by "a while". Weeks,
> months, years?

Two major releases is almost certainly less than six months. Or, if
you prefer, I can guarantee that the removal warning will be in a
release that will come out no later than a week after EAPI 4 goes live,
and that the removal can go ahead three months after that.

-- 
Ciaran McCreesh

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

      reply	other threads:[~2009-12-11 22:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-10 20:51 [gentoo-pms] kdebuild-1 conditionals Christian Faulhammer
2009-12-11 15:50 ` [gentoo-pms] " Ulrich Mueller
2009-12-11 17:08   ` Ciaran McCreesh
2009-12-11 18:24     ` Ulrich Mueller
2009-12-11 18:38       ` Ciaran McCreesh
2009-12-11 20:35         ` Brian Harring
2009-12-11 20:57           ` Ciaran McCreesh
2009-12-11 21:08             ` Brian Harring
2009-12-11 21:27               ` Ciaran McCreesh
2009-12-11 22:24               ` David Leverton
2009-12-16 18:21     ` Ulrich Mueller
2009-12-16 18:25       ` Ciaran McCreesh
2009-12-16 18:38         ` Ulrich Mueller
2009-12-16 18:46           ` Ciaran McCreesh
2010-01-04 15:26   ` Christian Faulhammer
2010-01-04 16:00     ` Ulrich Mueller
2010-01-09 15:03       ` Christian Faulhammer
2010-01-09 17:34         ` Ulrich Mueller
2010-01-10 17:01           ` Christian Faulhammer
2010-01-10 17:04           ` Ciaran McCreesh
2010-01-10 17:12             ` Ulrich Mueller
2010-01-11  8:41               ` Christian Faulhammer
2009-12-11 16:59 ` [gentoo-pms] " Brian Harring
2009-12-11 18:20   ` Ciaran McCreesh
2009-12-11 21:26     ` Ulrich Mueller
2009-12-11 21:34       ` Ciaran McCreesh
2009-12-11 21:50         ` Ulrich Mueller
2009-12-11 21:58           ` Ciaran McCreesh [this message]

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=20091211215831.09244f04@snowmobile \
    --to=ciaran.mccreesh@googlemail.com \
    --cc=fauli@gentoo.org \
    --cc=ferringb@gmail.com \
    --cc=gentoo-pms@lists.gentoo.org \
    --cc=ulm@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