public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Troy Dack <tad@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Improving Portage Watch script
Date: 15 Jun 2003 04:24:10 +1000	[thread overview]
Message-ID: <1055615050.2388.6.camel@carbon.internal.lan> (raw)
In-Reply-To: <200306141957.01121.rcm@sasaska.net>

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

On Sun, 2003-06-15 at 03:57, Rafael Cordones Marcos wrote:
> 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!

Would a cvs diff on use.desc work? You can even get this from the webcvs
frontend.

> 2.- Differentiating between updated packages and new packages
<snip>
> 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!

Both.  There is the echangelog tool that makes ChangeLog entries easy,
but some devs like to hand roll them (I'm not 100% sure if policy was
formalised to make echangelog compulsory)
-- 
Troy Dack        "Yes, yes, I know that, Sydney ... Everybody knows that!
tad@gentoo.org    ... But look: Four wrongs squared, minus two wrongs to 
                  the fourth power, divided by this formula, do make a
                  right." -- Gary Larson

Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x4D90BE3C
Key fingerprint = 1F3D 6C15 16AA 09D5 0C96  92E5 FD89 16F9 4D90 BE3C
 

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

  reply	other threads:[~2003-06-14 18:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-14 17:57 [gentoo-dev] Improving Portage Watch script Rafael Cordones Marcos
2003-06-14 18:24 ` Troy Dack [this message]
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=1055615050.2388.6.camel@carbon.internal.lan \
    --to=tad@gentoo.org \
    --cc=gentoo-dev@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