[gentoo-dev] Improving Portage Watch script

[gentoo-dev] Improving Portage Watch script

[Rafael Cordones Marcos]

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

Re: [gentoo-dev] Improving Portage Watch script

[Troy Dack]

[-- 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 --]

Re: [gentoo-dev] Improving Portage Watch script

[Todd Berman]

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

On Sat, 2003-06-14 at 13: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!
> 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!
The Changelogs are created by a small script called echangelog, so its
pretty easy to handle :)

--Todd

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