public inbox for gentoo-council@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Harring <ferringb@gmail.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: ciaranm@googlemail.com, gentoo-council@lists.gentoo.org,
	gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-council] Re: [gentoo-pms] kdebuild-1 conditionales
Date: Mon, 14 Dec 2009 12:58:17 -0800	[thread overview]
Message-ID: <20091214205817.GF6344@hrair> (raw)
In-Reply-To: <200912141201.04887.vapier@gentoo.org>

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

Pulling the thread back since the next chunk of is is going 
completely cyclical/misdirection if left as is..


On Mon, Dec 14, 2009 at 12:01:03PM -0500, Mike Frysinger wrote:
> On Monday 14 December 2009 10:14:37 Ciaran McCreesh wrote:
> > On Sun, 13 Dec 2009 21:31:11 -0500 Mike Frysinger wrote:
> > > yet crap that was explicitly never official or in used in the tree
> > > you feel you have a right to keep in the PMS.
> > 
> > It was added at the request of the Gentoo KDE team. It wasn't added
> > because I wanted it; it was added because Gentoo developers asked for
> > it. I realise you like to pretend that the people who asked for it
> > never existed, but the fact is they did, and it would be irresponsible
> > of Gentoo to make users suffer because of internal politicking.
> 
> great !  so when are you going to add these features that have existed for 
> years in portage to the PMS ?  your logic is complete crap.
> 
> > > it doesnt belong there, it never has, so delete it/branch it already.
> > 
> > You still haven't explained why it's better to delete it now than to do
> > a controlled removal that won't affect users.
> 
> and you have yet to show how your PM behavior is relevant one bit to the PMS 
> here.  removing unofficial crap from the PMS has no bearing whatsoever on 
> ebuilds that require unofficial PMs.  keep the crap in your PM forever for all 
> i care.

The fact Ciaran is explicitly ducking is that pulling KDEBUILD out of 
PMS in no shape or form actually screws those users.  Paludis created 
the eapi extension for them to use, it's their responsibility for 
maintaining the env or giving the uesrs a migration path away from it.  
The responsibility is at the PM level.

PMS is irrelevant to that.  I seriously doubt any user of KDEBUILD 
Ciaran is worried about will go looking in PMS for a description of 
how to get out of that mess... further, I seriously doubt anyone of 
those users ever looked at KDEBUILD in PMS in the first place- they 
were consumers at best.  Gentoo kde devs may've, but they're not the 
ones involved in the "oh think of the children!" claims of why the 
spec must stay in official docs.

I already suggested a workable compromise- punt it out of PMS, add a 
section to PMS of unofficial/experimental eapis w/ urls to those 
docs/versions of PMS.  We get the doc back to official EAPIs and a 
fair bit easier to edit, Ciaran gets his little hook to quiet him 
down.

Via this, if a dev *really* wanted to track down KDEBUILD and was 
completely incompetent in their googling skills, they still would find 
the spec.

As for users... no user is going to look at PMS for information on 
what's going on w/ paludis/KDEBUILD/the gentoo kde overlay.  Kindly 
drop the "think of the children/user" cry- it's not relevant to PMS, 
only to how paludis maintaing KDEBUILD support.

If that's not enough, just leave it to a fricking council vote.  
Already had a week of this stonewalling, it's wasting folks time (and 
nerves) dealing w/ it any further.

~harring

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

  parent reply	other threads:[~2009-12-14 21:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20091210214848.7d070ab2@gentoo.org>
     [not found] ` <20091210222730.5df0df14@snowmobile>
     [not found]   ` <20091211081754.GA6529@hrair>
     [not found]     ` <20091211135750.1c24a3fd@snowmobile>
     [not found]       ` <19234.23228.586356.915011@a1i15.kph.uni-mainz.de>
     [not found]         ` <20091211170245.053f6f16@snowmobile>
     [not found]           ` <19234.32055.471891.86138@a1i15.kph.uni-mainz.de>
2009-12-11 17:18             ` [gentoo-council] Re: [gentoo-pms] kdebuild-1 conditionales 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-13 12:21                     ` Petteri Räty
2009-12-13  3:45                   ` Mike Frysinger
2009-12-13 19:30                     ` Ciaran McCreesh
2009-12-13 20:16                       ` Jorge Manuel B. S. Vicetto
2009-12-13 20:20                         ` Ciaran McCreesh
2009-12-14  2:31                       ` Mike Frysinger
2009-12-14 15:14                         ` Ciaran McCreesh
2009-12-14 17:01                           ` Mike Frysinger
2009-12-14 18:21                             ` Ciaran McCreesh
2009-12-14 21:56                               ` Mike Frysinger
2009-12-14 20:58                             ` Brian Harring [this message]
2009-12-14 19:00               ` Ned Ludd
2009-12-14 19:15                 ` Nirbheek Chauhan
2009-12-14 19:17                   ` David Leverton
2009-12-14 19:24                 ` Ciaran McCreesh
2009-12-14 21:57                   ` Mike Frysinger

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=20091214205817.GF6344@hrair \
    --to=ferringb@gmail.com \
    --cc=ciaranm@googlemail.com \
    --cc=gentoo-council@lists.gentoo.org \
    --cc=gentoo-pms@lists.gentoo.org \
    --cc=vapier@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