Thanks. That's basically what I was thinking, only it never occurred to me at all until after the package was installed. I'll fix it. Which leads me to my next question. What's the proper way to do another release of my package? I changed the control files, did a dch -i, and stuff, and did dpkg-buildpackage and it didn't generate a new .changes file, just a .diff and a .dsc??? What's the proper procedure for creating a new release? Thanks, -Steven On Mon, Aug 14, 2000 at 09:04:49PM -0700, Seth Cohn wrote: > > So, I just created a new package. Should I have merged the > > changelogs into one, and made the packages look similar? > > Yes. If the package name is the same, you should have. > The package should as cleanly as possible replace the old one. > > History is important, even if it's just "new version upstream, new > maintainer, newly re-packaged.", and the rest of the changelog is > useless. It's still history of the package, and someone might CHOOSE to > revert and stay with the older version given a major change like that. > > apt-get upgrade will install your package, and the user has a right to be > able to read the changelog and the readmes and understand what happened. > > Seth > >
Attachment:
pgpnFoOB3F3iT.pgp
Description: PGP signature