Hi,
I've been using Debian for years and one of the question I've always
been afraid to ask is: why are Debian changelogs always so succint?
Is there a workflow or something else I can do to actually get an actual summary of upstream changes, without jumping through loops trying to
reach the upstream project itself? Ideally this is something I would
like to do when upgrading my Debian packages.
Usually if the upstream provides a list of changes, it is included in /usr/share/<package-name>. But there isn't a standard for its name
(and much less for its contents), so look for names like NEWS,
Changelog, etc. Often it is gzipped.
Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> writes:
Usually if the upstream provides a list of changes, it is included in
/usr/share/<package-name>. But there isn't a standard for its name
(and much less for its contents), so look for names like NEWS,
Changelog, etc. Often it is gzipped.
The path you probably mean is /usr/share/doc/<package-name>
I didn't think about looking there and now I've found a lot of
changelogs. I'll keep it in mind.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 546 |
Nodes: | 16 (2 / 14) |
Uptime: | 45:10:57 |
Calls: | 10,392 |
Files: | 14,066 |
Messages: | 6,417,260 |