public inbox for gentoo-pms@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: Brian Harring <ferringb@gmail.com>
Cc: gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] kdebuild-1 conditionales
Date: Fri, 11 Dec 2009 13:57:50 +0000	[thread overview]
Message-ID: <20091211135750.1c24a3fd@snowmobile> (raw)
In-Reply-To: <20091211081754.GA6529@hrair>

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

On Fri, 11 Dec 2009 00:17:54 -0800
Brian Harring <ferringb@gmail.com> wrote:
> On Thu, Dec 10, 2009 at 10:27:30PM +0000, Ciaran McCreesh wrote:
> > * Don't mess with kdebuild until you're sure that no-one has any
> >   kdebuild packages installed.
> 
> I'm not looking to start a fight, and frankly after a year or so I've 
> learned to just subconsciously/automatically ignore kdebuild, but why 
> exactly must this be in pms?

Because we have not yet established that no users have kdebuild things
installed. Thus, package managers that support it have to go on
supporting it.

Once kdebuild can be safely removed from package managers that have
supported it, it can then be removed from PMS.

> It's experimental w/ low user acceptance, and was fundamentally 
> outside the gentoo mainstream.  If long term maintenance of it is 
> desired for anyone who hasn't yet punted those ebuilds from their 
> vdb, maintain it in a branch rather then the effective head (don't 
> make the mainline suffer maintenance for something that was outside 
> mainline).

Branches are for use when you can't use better mechanisms. We have
better mechanisms.

-- 
Ciaran McCreesh

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

  parent reply	other threads:[~2009-12-11 14:13 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-10 20:48 [gentoo-pms] kdebuild-1 conditionales Christian Faulhammer
2009-12-10 22:27 ` Ciaran McCreesh
2009-12-11  6:08   ` Ulrich Mueller
2009-12-11 13:56     ` Ciaran McCreesh
2009-12-11 15:02       ` Ulrich Mueller
2009-12-11 17:06         ` Ciaran McCreesh
2009-12-11 17:26           ` Ulrich Mueller
2009-12-13 14:13         ` Ciaran McCreesh
2009-12-11 15:03     ` David Leverton
2009-12-11  8:17   ` Brian Harring
2009-12-11 10:45     ` Maciej Mrozowski
2009-12-11 13:59       ` Ciaran McCreesh
2009-12-11 14:23         ` Christian Faulhammer
2009-12-11 17:07           ` Ciaran McCreesh
2009-12-11 13:57     ` Ciaran McCreesh [this message]
2009-12-11 14:44       ` Ulrich Mueller
2009-12-11 17:02         ` Ciaran McCreesh
2009-12-11 17:11           ` Ulrich Mueller
2009-12-11 17:18             ` Ciaran McCreesh
2009-12-11 17:34               ` Ulrich Mueller
2009-12-11 17:43                 ` Ciaran McCreesh
2009-12-11 18:14                   ` Ulrich Mueller
2009-12-11 18:27                     ` Ciaran McCreesh
2009-12-11 19:42                       ` Brian Harring
2009-12-11 19:53                         ` Ciaran McCreesh
2009-12-11 20:30                           ` Brian Harring
2009-12-11 20:54                             ` Ciaran McCreesh
     [not found]                   ` <200912122245.50521.vapier@gentoo.org>
2009-12-13 19:30                     ` [gentoo-council] " Ciaran McCreesh
     [not found]                       ` <200912132131.13308.vapier@gentoo.org>
2009-12-14 15:14                         ` Ciaran McCreesh
     [not found]                           ` <200912141201.04887.vapier@gentoo.org>
2009-12-14 18:21                             ` Ciaran McCreesh
2009-12-14 20:58                             ` Brian Harring
     [not found]               ` <1260817256.7072.7.camel@hangover>
2009-12-14 19:24                 ` Ciaran McCreesh
2009-12-16 22:50   ` Christian Faulhammer
2009-12-16 23:08     ` Ciaran McCreesh

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=20091211135750.1c24a3fd@snowmobile \
    --to=ciaran.mccreesh@googlemail.com \
    --cc=ferringb@gmail.com \
    --cc=gentoo-pms@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