From: Nirbheek Chauhan <nirbheek.chauhan@gmail.com>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] Your part on ideas/issues for Google Summer of Code 2010
Date: Fri, 5 Mar 2010 11:51:22 +0530 [thread overview]
Message-ID: <8b4c83ad1003042221j420f5582mbd0d72ab96c51a2a@mail.gmail.com> (raw)
In-Reply-To: <4B904ED2.2030605@gentoo.org>
On Fri, Mar 5, 2010 at 5:52 AM, Sebastian Pipping <sping@gentoo.org> wrote:
> On 03/04/10 08:17, Arun Raghavan wrote:
>> There's bumpchecker too:
>> http://git.overlays.gentoo.org/gitweb/?p=proj/gentoo-bumpchecker.git;a=summary
>
> Is there documentation on this besides the code?
>
There's a command help list when you run the tool, but besides that,
nothing. Essentially you run a "bumpchecker" tool and that generates a
static html page after parsing upstream versions and portage/overlay
status.
> What's the status of this?
> - Is it ready to use?
It's already being used by the gnome and x11 herds. Here are sample
(somewhat outdated) pages:
http://dev.gentoo.org/~leio/gnome/gnome2.28.html
http://dev.gentoo.org/~leio/gnome/gnome2.26.html
http://dev.gentoo.org/~eva/gnome/gnome-2.28.2.html
Recently, patches for perl package support floated around, but I'm not
sure what happened to them.
> - if not could it serve as a base?
> - What use cases does it handle?
>
Just one: checking the progress of upstream package versions with
portage/overlay package versions.
This is why grumpy was envisioned. Besides having information about
upstream/downstream progress, it would have information about bugs,
stable/unstable keywords, p.mask, repoman/pcheck runs, test failures,
etc.
--
~Nirbheek Chauhan
Gentoo GNOME+Mozilla Team
next prev parent reply other threads:[~2010-03-05 6:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 0:03 [gentoo-soc] Your part on ideas/issues for Google Summer of Code 2010 Sebastian Pipping
2010-03-04 7:13 ` [gentoo-soc] " Hans de Graaff
2010-03-26 22:18 ` Sebastian Pipping
2010-03-04 7:17 ` [gentoo-soc] " Arun Raghavan
2010-03-04 7:52 ` Nirbheek Chauhan
2010-03-05 0:21 ` Sebastian Pipping
2010-03-05 0:22 ` Sebastian Pipping
2010-03-05 6:21 ` Nirbheek Chauhan [this message]
2010-03-05 6:26 ` Nirbheek Chauhan
2010-03-28 18:15 ` Hans de Graaff
2010-03-05 5:20 ` [gentoo-soc] " Zac Medico
2010-03-05 15:43 ` Sebastian Pipping
2010-03-06 0:51 ` Zac Medico
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=8b4c83ad1003042221j420f5582mbd0d72ab96c51a2a@mail.gmail.com \
--to=nirbheek.chauhan@gmail.com \
--cc=gentoo-soc@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