1 |
On Sun, 2003-06-15 at 03:57, Rafael Cordones Marcos wrote: |
2 |
> Hi, |
3 |
> |
4 |
> I want to improve the current script that generates the Portage Watch section |
5 |
> in GWN. The two problems I am focusing right now are: |
6 |
> |
7 |
> 1.- Listing the USE variables that were added or removed since a given date. |
8 |
> |
9 |
> I have been looking around Portage but I cannot find any ChangeLog where I can |
10 |
> get this info. A /usr/portage/profiles/use.desc ChangeLog would be perfect! |
11 |
|
12 |
Would a cvs diff on use.desc work? You can even get this from the webcvs |
13 |
frontend. |
14 |
|
15 |
> 2.- Differentiating between updated packages and new packages |
16 |
<snip> |
17 |
> One more thing, are ChangeLog files in packages automagically generated from |
18 |
> CVS or are they hand-edited by developers? If they are hand edited then I am |
19 |
> going to find errors in the format. I mean that humans commit errors and, for |
20 |
> instance, some dev can forget to write the "*" at the begining of a ChangeLog |
21 |
> entry! |
22 |
|
23 |
Both. There is the echangelog tool that makes ChangeLog entries easy, |
24 |
but some devs like to hand roll them (I'm not 100% sure if policy was |
25 |
formalised to make echangelog compulsory) |
26 |
-- |
27 |
Troy Dack "Yes, yes, I know that, Sydney ... Everybody knows that! |
28 |
tad@g.o ... But look: Four wrongs squared, minus two wrongs to |
29 |
the fourth power, divided by this formula, do make a |
30 |
right." -- Gary Larson |
31 |
|
32 |
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x4D90BE3C |
33 |
Key fingerprint = 1F3D 6C15 16AA 09D5 0C96 92E5 FD89 16F9 4D90 BE3C |