public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rafael Cordones Marcos <rcm@sasaska.net>
To: gentoo-dev@gentoo.org
Cc: Pablo Pita Leira <pablo.leira@pitagoral.com>,
	Bob Miller <kbob@jogger-egg.com>
Subject: [gentoo-dev] Improving Portage Watch script
Date: Sat, 14 Jun 2003 19:57:01 +0200	[thread overview]
Message-ID: <200306141957.01121.rcm@sasaska.net> (raw)

Hi,

I want to improve the current script that generates the Portage Watch section 
in GWN. The two problems I am focusing right now are:

1.- Listing the USE variables that were added or removed since a given date.

I have been looking around Portage but I cannot find any ChangeLog where I can 
get this info. A /usr/portage/profiles/use.desc ChangeLog would be perfect!

2.- Differentiating between updated packages and new packages

For this I think I can manage by looking at the last entry of the ChangeLog 
file and extracting the date from it. Example:
/usr/portage/app-cdr/k3b/ChangeLog

<file-contents>
[...]
*k3b-0.5.1 (1 Feb 2002)

  1 Feb 2002; G.Bevin <gbevin@gentoo.org> ChangeLog :

[...]
</file-contents>

One more thing, are ChangeLog files in packages automagically generated from 
CVS or are they hand-edited by developers? If they are hand edited then I am 
going to find errors in the format. I mean that humans commit errors and, for 
instance, some dev can forget to write the "*" at the begining of a ChangeLog 
entry!

Thanks for your time!

/Rafa

-- 
Rafael Cordones Marcos
rcm@sasaska.net
http://www.sasaska.net

"La diferencia entre una democracia y una dictadura
consiste en que en la democracia puedes votar antes
de obedecer las ordenes." -- Bukowski, C. 


--
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2003-06-14 17:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-14 17:57 Rafael Cordones Marcos [this message]
2003-06-14 18:24 ` [gentoo-dev] Improving Portage Watch script Troy Dack
2003-06-14 18:28 ` Todd Berman

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=200306141957.01121.rcm@sasaska.net \
    --to=rcm@sasaska.net \
    --cc=gentoo-dev@gentoo.org \
    --cc=kbob@jogger-egg.com \
    --cc=pablo.leira@pitagoral.com \
    /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