Re[2]: Debian package [was Re: Mail::Box::IMAP4]

> That is the reason why I would add some guides how to make a package for
> those
> which would like to have "the best and the latest". This is "one time"
> job.

Not to beat a dead horse, but it's really only a one time job to setup the debian/ directory. 
After that work is done, you just need to update debian/Changelog for each release.  The
control and rules files need only be updated when the dependencies and build procedures change.
 This is slightly oversimplified.  I just wanted to make sure the actual work involved is
somewhat represented.

And again, you can use the patch from the debian maintainer as the basis.  Even if you don't
keep it 100% up to date it makes it easier for the end user to build a package as well as the
debian maintainer.  In fact, you'd probably find he (the debian maintainer) will feed you
patches when he needs those files updated (he would have to comment on such an arrangement,
however).  


take care,
jason