| 1 |
On Fri, Mar 12, 2010 at 04:16:05PM +0100, Angelo Arrifano wrote: |
| 2 |
> Hello all, |
| 3 |
> |
| 4 |
> [Speaking as user] I find myself many times stumbling through package |
| 5 |
> ChangeLogs to see what is new/changed after a emerge -u world. As some |
| 6 |
> of you might agree, this is time consuming. |
| 7 |
> |
| 8 |
> What do you people think on a new pkg_changelog function that would |
| 9 |
> instruct the ebuild how to retrieve this kind of information from the |
| 10 |
> package? Most of packages have a somewhat standard place for it in the |
| 11 |
> source tree, so I guess a default pkg_changelog function could, in |
| 12 |
> theory, be implemented. |
| 13 |
> |
| 14 |
> This function could be then called at user request by means of e.g. |
| 15 |
> emerge --showchangelog <atom> or at the end of emerge update (controlled |
| 16 |
> through a FEATURES="show-changelog" or something). |
| 17 |
|
| 18 |
Actually there is already an option for emerge to show the changelogs |
| 19 |
of packages that will be upgraded. Take a look at the --changelog |
| 20 |
option for emerge. It can be used along with --pretend to show you the |
| 21 |
changelogs of packages that will be upgraded. |
| 22 |
|
| 23 |
Thanks, |
| 24 |
|
| 25 |
William |
Archives