On Sun, 4 Oct 2009, Paul Wise wrote:
So as long as it is uploaded before the freeze date you should be fine.
Thank you.
Most Standards-Version updates are of the form "Bump Standards-Version, no changes needed" and such updates should not be done unless they accompany some other update like fixing bugs or adding a new upstream version.
I'm thinking about the whole thing only because a new upstream version is not impossible (documentation changes only).
Write an article for debaday.debian.net about lbzip2 to promote it and get more users/testers.
I didn't know about debaday. I'll do this.
Have the package description and manual page reviewed by the Smith Review Project: http://wiki.debian.org/I18n/SmithReviewProject
Definitely.
Take a look at the FreeBSD port and see if the Makefile patch is appropriate to include upstream or if not, contact the port maintainer about it.
The FreeBSD port creator/maintainer, Gábor Kövesdán, personally offered to do the port [0], and I gratefully accepted (obviously). We already discussed the Makefile patch and concluded that the FreeBSD port needs it, and that upstream can't merge it. A minimal justification sounds like: (1) the port doesn't compile with -D _XOPEN_SOURCE=500, (2) SUSv2 requires -D _XOPEN_SOURCE=500 [1], and upstream is written against SUSv2.
No changes are planned for the upstream Makefile, so maintaining the patch shouldn't be much of a burden, hopefully.
Document in the manual page or README the TAR_OPTIONS environment variable and how to make tar use lbzip2 by default.
I'm not sure if adding --use=lbzip2 to TAR_OPTIONS was any more useful than adding any --use=compressor option; you'd lose the ability to create non-compressed tar files. (Or you'd have to explicitly pass --use=cat on the command line.) You'd also be unable to extract plain tar archives. (Or you'd have to explicitly pass some identity filter with --use on the command line that doesn't choke on -d.)
Talk to the upstream tar maintainers about ways to make tar detect if lbzip2 is available and use it instead of bzip2.
In that case, tar should support pbzip2 as well. I'll try. Much obliged, lacos [0] http://hup.hu/node/66857#comment-714251 [1] http://www.opengroup.org/onlinepubs/007908775/xsh/compilation.html
