| 1 |
As the latest long thread has shown, there seems to be a split (it is hard to |
| 2 |
tell exactly) on whether or not alternative package managers, that support |
| 3 |
Gentoo ebuilds to some degree, should be added to the tree and supported. |
| 4 |
Supported in this case means having their own profiles which may or may not |
| 5 |
work with Portage. There are currently a few different Portage rewrites, or |
| 6 |
alternatives, whatever you want to call them, and all of them have their own |
| 7 |
unique features being added to them which make them incompatible with Portage. |
| 8 |
Some don't even emulate Portage's "broken" behaviour which could also cause |
| 9 |
QA problems for us if we add the package to the tree. If a package is in the |
| 10 |
tree, it is implicitly stating that we are going to offer some level of |
| 11 |
support for that application, and it increases workload for everyone that |
| 12 |
may have an ebuild that works with one package manager and not another. |
| 13 |
|
| 14 |
Therefore, I am requesting at the next Council meeting that they discuss |
| 15 |
and decide on how we want to handle problems like this in general. This |
| 16 |
is not going to be the last time that someone wants to add their rewrite/ |
| 17 |
alternative of Portage to the tree. It should be decided if it is really |
| 18 |
in the best interests of Gentoo, its users, and developers to be adding |
| 19 |
these new managers to our own tree, instead of having them host their |
| 20 |
altered work on their own infrastructure. |
| 21 |
|
| 22 |
As the QA lead, I am requesting that until the Council convenes and decides |
| 23 |
on how we should proceed, that we not add anything else to the tree |
| 24 |
for the sole reason of supporting another package manager's features. |
| 25 |
This includes profiles or any other packages. This will reduce |
| 26 |
headaches for all of us, and hopefully cut down on needless arguments |
| 27 |
that get us no where. |
| 28 |
|
| 29 |
Thanks, |
| 30 |
|
| 31 |
-- |
| 32 |
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86) |
| 33 |
email - halcy0n AT gentoo DOT org |
| 34 |
mark AT halcy0n DOT com |
| 35 |
web - http://dev.gentoo.org/~halcy0n/ |
| 36 |
http://www.halcy0n.com |
Archives