1 |
On Fri, Mar 12, 2010 at 04:51:02PM +0100, Angelo Arrifano wrote: |
2 |
> On Sex, 2010-03-12 at 09:33 -0600, William Hubbs wrote: |
3 |
> > On Fri, Mar 12, 2010 at 04:16:05PM +0100, Angelo Arrifano wrote: |
4 |
> > > Hello all, |
5 |
> > > |
6 |
> > > [Speaking as user] I find myself many times stumbling through package |
7 |
> > > ChangeLogs to see what is new/changed after a emerge -u world. As some |
8 |
> > > of you might agree, this is time consuming. |
9 |
> > > |
10 |
> > > What do you people think on a new pkg_changelog function that would |
11 |
> > > instruct the ebuild how to retrieve this kind of information from the |
12 |
> > > package? Most of packages have a somewhat standard place for it in the |
13 |
> > > source tree, so I guess a default pkg_changelog function could, in |
14 |
> > > theory, be implemented. |
15 |
> > > |
16 |
> > > This function could be then called at user request by means of e.g. |
17 |
> > > emerge --showchangelog <atom> or at the end of emerge update (controlled |
18 |
> > > through a FEATURES="show-changelog" or something). |
19 |
> > |
20 |
> > Actually there is already an option for emerge to show the changelogs |
21 |
> > of packages that will be upgraded. Take a look at the --changelog |
22 |
> > option for emerge. It can be used along with --pretend to show you the |
23 |
> > changelogs of packages that will be upgraded. |
24 |
> |
25 |
> For a moment, you really tricked me into believing I've been missing |
26 |
> this feature. Specially by reading man emerge: |
27 |
> "This will show the ChangeLog entries for all the packages" |
28 |
> btw: shouldn't it read "ebuilds" here? /\ |
29 |
|
30 |
To me, if you change that wording to "ebuilds", you mean there will be a |
31 |
separate changelog for each *.ebuild file, so I would disagree with this |
32 |
change. |
33 |
|
34 |
> What I meant originally was to show the ChangeLog of the package |
35 |
> (ChangeLog inside source tree), not the ebuild ChangeLog. |
36 |
|
37 |
Not all upstreams provide changelogs (take a look at openrc as an |
38 |
example), so I'm not sure we could do this. Also, if we did, which file |
39 |
should we show (ChangeLog, NEWS, README ?) and how much of the file |
40 |
should we show? |
41 |
|
42 |
I'm not sure that there is an easy way to implement something like this. |
43 |
|
44 |
William |