From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] I want to steal your tools
Date: Sun, 03 Feb 2008 20:01:27 +0200 [thread overview]
Message-ID: <1202061687.19624.12.camel@localhost> (raw)
In-Reply-To: <1202022636.18533.3.camel@ip6-localhost>
[-- Attachment #1: Type: text/plain, Size: 1299 bytes --]
On P, 2008-02-03 at 08:10 +0100, Hans de Graaff wrote:
> On Sat, 2008-02-02 at 22:54 -0800, Alec Warner wrote:
>
> > So reply with a URL pointing at your tool*.
>
> For XEmacs there is the pebuild script which tracks upstreams packages
> and automatically bumps ebuilds for them when newer versions are
> available: http://www.gentoo.org/proj/en/lisp/emacs/pebuild.gz
>
> For Ruby Richard just wrote a similar tool to track which upstream gems
> have a newer version available:
> http://dev.gentoo.org/~rbrown/ruby_scripts/
The GNOME team uses a similar purpose tool for packages released to
GNOME mirrors.
It's currently maintained by dang on a git repository of his, located
here:
git://apollo.fprintf.net/depchecker
It produces a result like this:
http://dev.gentoo.org/~leio/gnome/gnome2.20.html
Which visualizes what version bumps we are missing for a given GNOME
release series.
There have been blue sky ideas how to improve something like this to a
lot more packages, including all hosted on GNOME mirrors and available
from gnomefiles.org lists (we have parse-able data available from them)
and more, but nothing has materialized as of yet.
--
Mart Raudsepp
Gentoo Developer
Mail: leio@gentoo.org
Weblog: http://planet.gentoo.org/developers/leio
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-02-03 18:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 6:54 [gentoo-dev] I want to steal your tools Alec Warner
2008-02-03 7:10 ` Hans de Graaff
2008-02-03 12:48 ` [gentoo-dev] " Dirk Tilger
2008-02-03 18:01 ` Mart Raudsepp [this message]
2008-02-03 7:34 ` Christian Faulhammer
2008-02-03 7:56 ` [gentoo-dev] " Josh Saddler
2008-02-03 11:53 ` Drake Wyrm
2008-02-03 12:24 ` Fabian Groffen
2008-02-03 16:05 ` Duncan Coutts
2008-02-03 16:56 ` Ciaran McCreesh
2008-02-03 20:21 ` [gentoo-dev] " Ryan Hill
2008-02-03 23:35 ` [gentoo-dev] " Petteri Räty
2008-02-04 20:51 ` [gentoo-dev] " Ryan Hill
2008-02-04 21:59 ` Ryan Hill
2008-02-04 22:05 ` Ciaran McCreesh
2008-02-04 22:29 ` Vlastimil Babka
2008-02-04 22:42 ` Ryan Hill
2008-02-04 22:53 ` Thomas de Grenier de Latour
2008-02-04 23:03 ` Ryan Hill
2008-02-05 1:50 ` Heath N. Caldwell
2008-02-05 3:21 ` Ryan Hill
2008-02-05 5:06 ` Jeroen Roovers
2008-02-05 13:28 ` Santiago M. Mola
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=1202061687.19624.12.camel@localhost \
--to=leio@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