On Wed, Apr 06, 2005 at 02:16:08PM +0200, Benjamin Mesing wrote: > I have a package which I develop on my own and which is debian native. > However due to historical reasons, I have a CHANGELOG file which is not > the debian/changelog file. > How should I handle this case? I am in favour of handling it like an > upstream package, meaning > 1. debian/changelog -> changelog.Debian > 2. CHANGELOG -> changelog > Is this appropriate? Why not? Use changelog.Debian for packaging changes and changelog for the application changes. Greetings Torsten
Attachment:
signature.asc
Description: Digital signature