public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] making the stable tree more up-to-date
Date: Mon, 21 Nov 2011 07:47:16 -0800	[thread overview]
Message-ID: <1321890436.24330.73.camel@big_daddy.dol-sen.ca> (raw)
In-Reply-To: <4ECA0EA3.8020407@gentoo.org>

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

On Mon, 2011-11-21 at 09:41 +0100, "Paweł Hajdan, Jr." wrote:

> I wrote a script,
> <http://git.overlays.gentoo.org/gitweb/?p=proj/arch-tools.git;a=blob;f=stabilization-candidates.py;hb=HEAD>,
> that scans the tree for packages that could be easily stabilized (all
> deps stable, no bugs).
> 

> Paweł

nice :)

you might want to consider adding the "trees=" parameter to the cp_all()
call.  It will limit the scan to only the trees passed.  Useful for
those that have overlays installed.

 line 41: for cp in portage.portdb.cp_all():

Also the cp_list() takes an optional mytree parameter as well
.
line 48: for cpv in portage.portdb.cp_list(cp):

The portdbapi also has some convenience functions,

getRepositoryName()
getRepositoryPath()

which you may be able to use instead of needing to pass the --repo path
in.  From what I understand is that many of you use the cvs tree for
your main gentoo tree rather than the normal rsync.
-- 
Brian Dolbec <dolsen@gentoo.org>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  parent reply	other threads:[~2011-11-21 15:48 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21  8:41 [gentoo-dev] making the stable tree more up-to-date "Paweł Hajdan, Jr."
2011-11-21 11:48 ` Ulrich Mueller
2011-11-21 12:14 ` Andreas K. Huettel
2011-11-21 12:24   ` "Paweł Hajdan, Jr."
2011-11-21 12:27   ` Rich Freeman
2011-11-21 13:12 ` James Broadhead
2011-11-21 15:47 ` Brian Dolbec [this message]
2011-11-23 14:27 ` [gentoo-dev] " Torsten Veller
2011-11-24 15:17   ` "Paweł Hajdan, Jr."
2011-11-24 16:35     ` Ian Stakenvicius
2011-11-24 17:12       ` Rich Freeman
2011-11-24 17:26         ` Pacho Ramos
2011-11-29 12:18         ` "Paweł Hajdan, Jr."
2011-11-25 16:39 ` [gentoo-dev] " Thomas Kahle
2011-11-25 19:06   ` Mr. Aaron W. Swenson
2011-11-29 12:17   ` "Paweł Hajdan, Jr."
2011-12-16 10:42 ` justin
2011-12-16 11:06   ` Agostino Sarubbo
2011-12-16 11:10     ` Anthony G. Basile
2011-12-16 11:21       ` Agostino Sarubbo
2011-12-16 11:46         ` justin
2011-12-18 10:59           ` [gentoo-dev] checking C*FLAGS used for build (was: making the stable tree more up-to-date) Michał Górny
2011-12-16 11:07   ` [gentoo-dev] making the stable tree more up-to-date Brian Harring
2011-12-16 13:27   ` "Paweł Hajdan, Jr."
2011-12-16 13:53     ` Rich Freeman
2011-12-16 14:05       ` Andreas K. Huettel
2011-12-16 18:40         ` Tim Harder
2011-12-16 14:12     ` justin
2011-12-17 15:25       ` "Paweł Hajdan, Jr."

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=1321890436.24330.73.camel@big_daddy.dol-sen.ca \
    --to=dolsen@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