Re: Native package with two changelogs
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?
I do this with quite a few of my packages. In many cases, the tarball I
release has a file named ChangeLog that is automatically maintained for
me by tla. It is far more detailed than a debian/changelog file usually
is, and contains details of interest to plenty of people besides Debian
users -- but may also be of interest to Debian users.