Bug 22429 – emerge -pl portage does not show anything

• Product: Portage Development
• Status: RESOLVED WONTFIX

[Description Rajiv Aaron Manglani (RETIRED) 2003-06-08 03:29:06 UTC]

'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.

[Comment 1 Rajiv Aaron Manglani (RETIRED) 2003-09-02 00:19:59 UTC]

*** Bug 27671 has been marked as a duplicate of this bug. ***

[Comment 2 Rajiv Aaron Manglani (RETIRED) 2003-09-02 00:20:33 UTC]

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>

[Comment 3 Alec Warner (RETIRED) 2005-07-30 07:37:18 UTC]

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.  :)

[Comment 4 Jason Stubbs (RETIRED) 2005-10-07 07:50:12 UTC]

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.