On Sun, Apr 24, 2016 at 8:02 PM, Nicholas D Steeves wrote: > If a package's changelog is published on a wiki, is it still necessary > and/or desirable to ship a changelog with the Debian package?
It could be useful, yes. > is something like the following the best solution: > > curl https://btrfs.wiki.kernel.org/index.php/Changelog | html2text | > sed '0,/(announcement)/d;/By version (linux kernel)/Q' | gzip -9 > > debian/local/changelog.gz I would instead get the raw mediawiki text (since it is the source for the page; I like to apply DFSG item 2 to everything) and use pandoc, Text::MediawikiFormat or similar to render it to a nicer plain text format at build time. Ideally you could convince upstream to do this as part of their release and build processes. https://btrfs.wiki.kernel.org/index.php?title=Changelog&action=raw > that the following is preferred?: > curl https://btrfs.wiki.kernel.org/index.php/Changelog | gzip -9 > > debian/local/changelog.html.gz Plain text is better IMO. > Given standards-version 3.9.7, this has to be done when preparing a > new version of the package, and not when building, correct? And to > actually add the changelog to the package, add the following to the > appropriate section of debian/rules: I would do the download just after uscan and the conversion from Mediawiki format at debian/rules build time. > If the upstream changelog was specific to just btrfs-progs, then I > would use the html version without question; however, because a > substantial portion of it does not pertain to the btrfs-progs package > itself, I wonder it's better to convert to text and cut the > non-applicable sections... Definitely cut the non-applicable sections. -- bye, pabs https://wiki.debian.org/PaulWise
