Re: Bug#95579: dpkg-parsechangelog (Re: NEWS.Debian support is here)
On Tue, Jul 08, 2003 at 01:46:49PM -0500, Adam Heath wrote: > On Tue, 8 Jul 2003, Matt Zimmerman wrote: > > This change wouldn't break the format or anything; it would only add some > > additional text to the Changes: field. Surely no programs depend on the > > _content_ of that field, do they? > > Well, that still doesn't help, as then you'd have to parse the output of the > Changes: field. I wouldn't need to parse it, just display it. All of the information that apt-listchanges actually needs is already parsed out by dpkg-parsechangelog. It's just that it eats all of the lines containing the email address and date of the uploads. For the most recent upload, this could be reconstructed from the information in the header, but that's pretty ugly, and the information from previous uploads (selected with -v) is lost forever. -- - mdz
Re: Bug#95579: dpkg-parsechangelog (Re: NEWS.Debian support is here)
On Tue, 8 Jul 2003, Matt Zimmerman wrote: > On Tue, Jul 08, 2003 at 01:11:46PM -0500, Adam Heath wrote: > > > On Sun, 6 Jul 2003, Matt Zimmerman wrote: > > > I filed a wishlist bug about this quite a long time ago (#95579), but > > > got no response. > > > > Hmm, maybe a library(perl) that gives all this information would be > > useful. Modifying the text output of dpkg-parsechangelog is difficult, as > > several programs parse it's output. > > This change wouldn't break the format or anything; it would only add some > additional text to the Changes: field. Surely no programs depend on the > _content_ of that field, do they? Well, that still doesn't help, as then you'd have to parse the output of the Changes: field.
