public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Harring <ferringb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] draft glep: multi-repo
Date: Sat, 17 Dec 2005 17:01:59 -0800	[thread overview]
Message-ID: <20051218010159.GF22142@nightcrawler.e-centre.net> (raw)
In-Reply-To: <20051218002448.04bac00f@snowdrop.home>

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

On Sun, Dec 18, 2005 at 12:24:48AM +0000, Ciaran McCreesh wrote:
> On Sat, 17 Dec 2005 16:14:15 -0800 Brian Harring <ferringb@gentoo.org>
> wrote:
> | What remaining straw men are there for ignoring the portage 
> | developers requests?
> 
> Asking you to specify how multiple repositories will work before I try
> to extend the GLEP to support multiple repositories is hardly a straw
> man argument.

Do you need to know how every bit of a car works to drive it?  No.

We're simply asking you to tag in a repo_id to your calls to portage.  
It's bloody simple, just need to know what you explicitly need from a 
news client standpoint.

Stop being a stubborn mule, and realize that you're trying to shove a 
feature into portage that *we* have to maintain, including your built 
in design flaw for N repos.

If you can't accept our criticism and suggestions for your glep, tough 
cookies, we're the ones stuck maintaining it, and the users are the 
one stuck when we expand portage functionality (thus breaking your 
implementation).


> *shrug* But if you prefer, I'll change the GLEP to
> support multiple repositories the way I'd like to see them done rather
> than the way you'd like.

Ciaranm, cut the word games and stupid threats.

If you can't work with others, and actually understand that they may 
not agree with your views (let alone be willing to have you dump a 
mess on them), I suggest you leave the distro and go work on your 
social skills.

Propose the glep however you want.

As long as the glep is around, I'm going to do the same you do- point 
out the flaws in it.  If you're unwilling to even nail down what is 
needed so that all parties are happy, that's fine- I would expect the 
council to realize the glep (heavily affecting the portage group, 
since server and client side mods fall on our head) needs to be worked 
out further and thus reject it.

Or, you stop debating the fact portage group might have a say in this, 
and start discussing what needs to be done so progress is made.

Balls in your court, you know we view it as unacceptable right now, if 
you're not willing to work with us there isn't much that can be done.

~harring

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

  reply	other threads:[~2005-12-18  1:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-17  8:17 [gentoo-dev] DRAFT GLEP: MULTI-REPO Andrew Muraco
2005-12-17  8:19 ` Andrew Muraco
2005-12-17 23:15 ` [gentoo-dev] draft glep: multi-repo Brian Harring
2005-12-17 23:25   ` Ciaran McCreesh
2005-12-18  0:14     ` Brian Harring
2005-12-18  0:24       ` Ciaran McCreesh
2005-12-18  1:01         ` Brian Harring [this message]
2005-12-18  1:08           ` Ciaran McCreesh
2005-12-18  1:31             ` Brian Harring

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=20051218010159.GF22142@nightcrawler.e-centre.net \
    --to=ferringb@gentoo.org \
    --cc=gentoo-dev@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