public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Christel Dahlskjaer <christel@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Alternative Gentoo package managers discussion request (for the council)
Date: Thu, 18 May 2006 00:23:58 +0100	[thread overview]
Message-ID: <1147908238.4723.7.camel@gaspode> (raw)
In-Reply-To: <20060517213845.GG10815@aerie.halcy0n.com>

On Wed, 2006-05-17 at 17:38 -0400, Mark Loeser wrote:
> As the latest long thread has shown, there seems to be a split (it is hard to
> tell exactly) on whether or not alternative package managers, that support
> Gentoo ebuilds to some degree, should be added to the tree and supported.
> Supported in this case means having their own profiles which may or may not
> work with Portage.  There are currently a few different Portage rewrites, or
> alternatives, whatever you want to call them, and all of them have their own
> unique features being added to them which make them incompatible with Portage.
> Some don't even emulate Portage's "broken" behaviour which could also cause
> QA problems for us if we add the package to the tree.  If a package is in the
> tree, it is implicitly stating that we are going to offer some level of
> support for that application, and it increases workload for everyone that
> may have an ebuild that works with one package manager and not another.
> 
> Therefore, I am requesting at the next Council meeting that they discuss
> and decide on how we want to handle problems like this in general.  This
> is not going to be the last time that someone wants to add their rewrite/
> alternative of Portage to the tree.  It should be decided if it is really
> in the best interests of Gentoo, its users, and developers to be adding
> these new managers to our own tree, instead of having them host their
> altered work on their own infrastructure.
> 
> As the QA lead, I am requesting that until the Council convenes and decides
> on how we should proceed, that we not add anything else to the tree
> for the sole reason of supporting another package manager's features.
> This includes profiles or any other packages.  This will reduce
> headaches for all of us, and hopefully cut down on needless arguments
> that get us no where.

Good call Mark. I second this request.


-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2006-05-17 22:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-17 21:38 [gentoo-dev] Alternative Gentoo package managers discussion request (for the council) Mark Loeser
2006-05-17 21:55 ` Ciaran McCreesh
2006-05-18 10:49   ` Paul de Vrieze
2006-05-18 12:16     ` Stephen Bennett
2006-05-18 13:34       ` Paul de Vrieze
2006-05-18 14:03         ` Stephen Bennett
2006-05-18 14:37           ` Paul de Vrieze
2006-05-18 15:24             ` Stephen Bennett
2006-05-18 16:19             ` Edward Catmur
2006-05-18 16:45               ` Stephen Bennett
2006-05-17 21:57 ` Henrik Brix Andersen
2006-05-17 22:21   ` Grant Goodyear
2006-05-17 23:23 ` Christel Dahlskjaer [this message]
2006-05-17 23:41   ` Christel Dahlskjaer
2006-05-17 23:52     ` George Prowse
2006-05-18 12:38 ` Ned Ludd

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=1147908238.4723.7.camel@gaspode \
    --to=christel@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