public inbox for gentoo-qa@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Loeser <halcy0n@gentoo.org>
To: gentoo-qa@lists.gentoo.org
Subject: Re: [gentoo-qa] Support of other package managers
Date: Tue, 16 May 2006 19:57:13 -0400	[thread overview]
Message-ID: <20060516235713.GA10815@aerie.halcy0n.com> (raw)
In-Reply-To: <446A4E17.8010203@gentoo.org>

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

Zac Medico <zmedico@gentoo.org> said:
> Yeah, I think what's really needed is a specification of what is allowed in
> gentoo's official portage tree.  Let's take "per-package use.mask" (bug
> 96368) as an example.  It could be implemented as package.use.mask or as
> package.mask + use deps.  Which will it be?  Will paludis, pkgcore, and portage
> all handle this functionality the same way or not?  If we're going to allow new
> features such as this into the official portage tree, we need to make sure that
> they conform to a specification that everyone has agreed upon.

This is the exact problem I'm trying to address.  You'll never get all
of the projects to agree, since they all want to go in slightly
different directions and do different things.  All three are great
ideas, but we should only support the one that is official for Gentoo,
and not make any changes to the tree.  (Note: changes here is any
modification or addition of files in the tree for the sole purpose of
working with an alternate package manager)

Either way, I think this is something we should hold off on for now, and
have the council decide upon.  We shouldn't just make these changes
without having some discussion taking place (the flamewar on g-dev@ is
not a discussion, and is only a small minority of people giving their
two cents).

Whatever the decision is, the addition of another package manager makes
QA harder to do since we have to consider all of them.  Adding a new
package manager and saying we don't support it, nor are we sure if we
will ever support it, does not seem acceptable at all to me.  The
decision should be made if we plan on supporting it so we can work on
actually supporting it, or if this should be a completely separate
project and they can work on their own to make changes to ebuilds which
support their own functionality.

-- 
Mark Loeser   -   Gentoo Developer (cpp gcc-porting qa toolchain x86)
email         -   halcy0n AT gentoo DOT org
                  mark AT halcy0n DOT com
web           -   http://dev.gentoo.org/~halcy0n/
                  http://www.halcy0n.com

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

  reply	other threads:[~2006-05-16 23:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-16 17:48 [gentoo-qa] Support of other package managers Mark Loeser
2006-06-13 19:17 ` Stephen Bennett
2006-05-16 19:56   ` Seemant Kulleen
2006-05-16 22:11     ` Zac Medico
2006-05-16 23:57       ` Mark Loeser [this message]
2006-05-17  2:54         ` Zac Medico
2006-05-17  6:13         ` Mike Frysinger
2006-05-17  6:48         ` Kevin F. Quinn
2006-05-17  0:21       ` Stephen Bennett
2006-06-13 20:40     ` Stephen Bennett

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=20060516235713.GA10815@aerie.halcy0n.com \
    --to=halcy0n@gentoo.org \
    --cc=gentoo-qa@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