On Wednesday 02 May 2001 10:28, Robert Bihlmeyer wrote: > [EMAIL PROTECTED] writes: > > When the upstream developer and the debian developer are the same person, > > it still makes sense to treat the package as a non-native package if > > there will ever be non-Debian releases. > > Ok, this only makes sense if (and as long as) you are both Debian > mainainer and lead upstream developer, so let's take this as granted. > > In this case you *may* choose to produce maintain a deb without a > Debian version (a "native" package). You should be aware that fixing a > bug in debian/rules will force you to up your version number, but > that's not so big a problem in my mind.
It doesn't require a version change. I recently fixed a packaging problem with Bonnie++ version 1.00b (for which I am both upstream and Debian maintainer) as 1.00b-1. Next version will be 1.00c! -- http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/projects.html Projects I am working on http://www.coker.com.au/~russell/ My home page
