public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <gentoo@mgorny.alt.pl>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Moving unmaintained packages to Sunrise
Date: Sun, 13 Jun 2010 10:41:43 +0200	[thread overview]
Message-ID: <20100613104143.4f61dbe7@pomiocik.lan> (raw)

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

Hello,

There are some packages which were 'readded' to the Sunrise overlay
after lying unmaintained in the tree for a long time and finally being
removed. One example could be net-im/ekg2 for removal of which I've been
personally waiting.

Although such a workflow 'works' indeed, for most of the users packages
are just removed. Even if they use Sunrise, the delay of few days
required in order to get the new ebuild rewritten and reviewed causes
them to remove and forget about the package. And in fact, gx86 states
it was 'removed'.

Currently, the Sunrise policy states that there could be added only
packages which are maintainer-wanted and thus not in gx86. For
maintainer-needed, there is a proxy-commit mechanism but it's a little
awkward, especially if the new ebuild is supposed to be written from
scratch (like ekg2 one was).

Wouldn't it be better to officially support moving unmaintained
packages directly into Sunrise? In this case by 'unmaintained' I mean
those which have open bugs assigned to 'maintainer-needed' for a long
time, and are potentially a candidates for the treecleaning (not
necessarily being in the removal queue yet).

The particular Sunrise user wanting to maintain the package suggests
moving it to Sunrise (to whom?). If developers agree on that, he is
allowed to prepare the Sunrise ebuild and even commit it to the
'sunrise' (non-public) tree.

When Sunrise dev does the final review, after which the package would
be moved to 'reviewed' (public) tree, he/she also masks the original
package in gx86 stating that the package is now maintained in Sunrise.
After 30 (or more) days, the masked gx86 packages are removed as usual.

The advantage of such a workflow is quite obvious -- instead of seeing
'removed' packages which they need to either copy to their own overlay
or abandon, users are advised to add 'sunrise' to their repository list
and use the user-maintained ebuild. And then the move is almost
transparent to current Sunrise users.

-- 
Best regards,
Michał Górny

<http://mgorny.alt.pl>
<xmpp:mgorny@jabber.ru>

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

             reply	other threads:[~2010-06-13  8:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-13  8:41 Michał Górny [this message]
2010-06-13  9:05 ` [gentoo-dev] Moving unmaintained packages to Sunrise Matti Bickel
2010-06-13 10:38 ` [gentoo-dev] " Duncan
2010-06-13 12:07   ` Markos Chandras
2010-06-13 14:27     ` Rémi Cardona
2010-06-13 16:35     ` Michał Górny
2010-06-13 16:39       ` Markos Chandras
2010-06-13 16:56       ` "Paweł Hajdan, Jr."
2010-06-13 14:26 ` [gentoo-dev] " Jorge Manuel B. S. Vicetto
2010-06-13 20:36   ` [gentoo-dev] " Duncan
2010-06-19 17:53     ` Thomas Sachau
2010-06-13 21:19   ` [gentoo-dev] " Petteri Räty
2010-06-13 23:48   ` Sebastian Pipping

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=20100613104143.4f61dbe7@pomiocik.lan \
    --to=gentoo@mgorny.alt.pl \
    --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