'emerge -pl portage' when there is a portage update does not show the portage changelog. i understand that /usr/portage/sys-apps/portage/ChangeLog says to go see some url in our cvs... 'emerge -pl portage' should say the same thing.
*** Bug 27671 has been marked as a duplicate of this bug. ***
i understand that the portage changelog is really long (bug #6870). but i think that 'emerge -pl portage' should at least print out the url to the portage changelog: <http://www.gentoo.org/cgi-bin/viewcvs.cgi/portage/ChangeLog?rev=HEAD&cvsroot=gentoo-src&content-type=text/vnd.viewcvs-markup> or <http://www.gentoo.org/cgi-bin/viewcvs.cgi/*checkout*/portage/ChangeLog?rev=HEAD&cvsroot=gentoo-src&content-type=text/plain>
The problem is that emerge -pl <package> has some nice code to detect package revisions in the Changelog and to print only relevant revisions. However, the portage Changelog has no revisions, just a URL to ViewCVS telling the user to go there for the full Changelog ( since it is in fact, huge ). You can basically do 3 things. 1. Write an exception into -l that says when we are dealing with portage, just print the Changelog verbatim which would get the URL out. This is a huge hack that IMHO will never happen. 2. Rewrite the Changelog that is distributed in the tree to have a couple of revisions, all pointing toward viewCVS. This is the simpliest fix IMHO. Just add a set of revisions that covers a wide range of versions so when people run emerge -l portage they get the viewCVS links relevant to the emerging version. 3. Deal with the fact that emerge -l doesn't work with all packages, Portage included. :)
2) doesn't work that way. It finds the first tag that matches the new version and the first tag that matches the existing version and then displays everything in between. This behaviour is broken anyway as arch and ~arch versions can move independently and have their ChangeLog's intertwined. Combine that with the fact that the ChangeLog is pretty much useless for users (and devs too for that matter) I'd be much more inclined to drop the --changelog option altogether.
