Incorporating patches best practice
The FLTK maintainer submitted a bug today to let me know that he's
created a change that will impact me:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633474
In the email, he attached a patch. I'm unsure of the best approach to
take for updating my package; I see three obvious choices:
1) Obviously not appropriate in the general case, but I could do a major
new release, since I've added a couple of big features since the last
deiban package.
2) Re-package the current package, but include the one patch, and ramp
the debian version suffix [to 0.16-2]
3) Re-package at the current version and ramp the debian version suffix,
but include the patch directly in the source; basically, change the main
source tarball to be the current svn version. Of course, that would include
the major changes I've made since I officially released 0.16...
I suspect that the best answer is #2, but that feels a little hokey when
I'm the upstream as well as the package maintainer.
Thanks,
Gary
Reply to: