* Marc Haber <mh+debian-de...@zugschlus.de> [2016-05-11 10:47:52 +0200]:
> >The third reason is the question of how much in detail the release > >notes should actually be. In a strange way in the past they were too > >short. That made me reluctant to suggest entries for low-popcon > >packages as their significance doesn't match the prominence of being > >mentioned in the notes. > > We could have a "show-release-notes" package containing a script that > scans (pre-upgrade) the installed packages and shows all release-notes > relevant to those packages. This would need the release notes to be in > a somewhat automatically-selectable format, most easily a http-served > directory somewhere with a packagename.txt for each package that has > relevant text that went past the package maintainer and the release > team. Some thought needs to go in there for the cases where package > foo is superseded by foo2. Most easily this could be a simple symlink > in the releasenotes directory. That really sounds like what apt-listchanges already does. -- Nicolas Dandrimont BOFH excuse #147: Party-bug in the Aloha protocol.
signature.asc
Description: Digital signature
