Well, dh7 has the same kind of heuristic[1] to detect the upstream ChangeLog
so the end result would be the same and when it doesn't detect it
correctly, the maintainer is supposed to add an override for
dh_install_changelogs and pass it explicitly.
If you really want to strip them for all dehelper-using packages, you have to
modify dh_installchangelogs to not install it in the first place.
[1] See dh_installchangelogs(1):
An upstream changelog file may be specified as an option. If none
is specified, a few common filenames are tried. (In compatibility
level 7 and above.)
On Wed, 16 Jun 2010, Martin Pitt wrote: git.debian. org/?p= collab- maint/cdbs. git;a=blob; f=1/rules/ debhelper. mk.in;h= b46838b2e5760a5 d9a1353477d6875 86118bf28b; hb=HEAD# l113
> Because it's (Debian's) cdbs which installs it in the first place :-)
>
> http://
>
> So this bit is not relevant for the dh7 port.
Well, dh7 has the same kind of heuristic[1] to detect the upstream ChangeLog changelogs and pass it explicitly.
so the end result would be the same and when it doesn't detect it
correctly, the maintainer is supposed to add an override for
dh_install_
If you really want to strip them for all dehelper-using packages, you have to elogs to not install it in the first place.
modify dh_installchang
[1] See dh_installchang elogs(1) :
An upstream changelog file may be specified as an option. If none
is specified, a few common filenames are tried. (In compatibility
level 7 and above.)
Cheers,
--
Raphaël Hertzog
Like what I do? Sponsor me: http:// ouaza.com/ wp/2010/ 01/05/5- years-of- freexian/ ouaza.com/ wp/2010/ 01/09/debian- related- goals-for- 2010/
My Debian goals: http://