gentoolkit tool request... when one does a emerge -up world, new packages are listed. Being able to see the changelogs BEFORE one runs -u world would make it easier for users to be selective as to which updates they want / need. suggested example usage: ./view-changelog --updates --- new changelogs of ebuilds ./view-changelog --package foo --- changelogs of package X (if possible... usually CHANGELOG) ./view-changelog --- same as ./view-changelog --help
Carpaski: I can do this in bash without too much trouble, but maybe an emerge world -up --verbose option of some sort is in order, comments?
./emerge --update --pretend --changelogs world
this one tagged as dup because Bug 6124 has actual patches for a solution *** This bug has been marked as a duplicate of 6124 ***
Ahm... 6124 isn't a patch... it's a hack. It's a shell script that shows the change log of ebuilds and the changelogs of a package if the changelog file exists within a 'standard' location. Yes, the author of 6124 is calling 6124 a hack. What I would like to see is portage do it's magic to fetch and unpack a file... possibly have a CHANGELOG field in the ebuild itself (CHANGELOG="${W}/ChangeLog")... show the user the changelog then ask the user if they want to merge the new package or not. After all packages have been selected yes or no... then go ahead and do the work. This is BEST done in portage itself... not a shell script calling ebuild and emerge -u -p ... emerge --update --viewchanges --pretend world emerge --update --changelogs --pretend world Doesn't matter to me
