1 |
Hello all, |
2 |
|
3 |
[Speaking as user] I find myself many times stumbling through package |
4 |
ChangeLogs to see what is new/changed after a emerge -u world. As some |
5 |
of you might agree, this is time consuming. |
6 |
|
7 |
What do you people think on a new pkg_changelog function that would |
8 |
instruct the ebuild how to retrieve this kind of information from the |
9 |
package? Most of packages have a somewhat standard place for it in the |
10 |
source tree, so I guess a default pkg_changelog function could, in |
11 |
theory, be implemented. |
12 |
|
13 |
This function could be then called at user request by means of e.g. |
14 |
emerge --showchangelog <atom> or at the end of emerge update (controlled |
15 |
through a FEATURES="show-changelog" or something). |
16 |
|
17 |
I know we are all busy with a lot of things and I know what Gentoo don't |
18 |
really need right now is more cruft in the ebuilds (just think on QA!). |
19 |
|
20 |
Regards, |
21 |
-- |
22 |
Angelo Arrifano AKA MiKNiX |
23 |
Gentoo Embedded/OMAP850 Developer |
24 |
Linwizard Developer |
25 |
http://www.gentoo.org/~miknix |
26 |
http://miknix.homelinux.com |