On Sat, 2009-02-28 at 20:14 -0800, Russ Allbery wrote: > Hm, I've seen upstreams switch from .tar.gz to .tar.bz2, but I've not seen > one switch from .tar.gz to .tgz or vice versa. Maybe my experience is > just limited, though. I'd be very surprised to see any upstream go back > to a plain .tar except by pure accident that would be quickly corrected. This was one of those 'just in case' style things. > I'm not completely sure where in here is the balance between helping > people not miss things and asking people to add ugly regexes to their > watch files that will never trigger (thus just annoying them). I have to > admit that I personally would tend not to add .tgz or .tbz extensions. I > don't have any upstreams that would ever name their tarballs that way > (they break the normal semantics of compression programs, so those > extensions are really broken), so it's just more visual complexity in the > watch file for no real purpose. Hmm, perhaps this should be a job for dehs or debexpo, which could run uscan and be a bit smarter about checking the results and expanding the regex to see if it matches anything else that exists. Hmm, or perhaps an option in uscan itself. > Incidentally, for .lzma, it looks like LZMA is dead and XZ is going to > replace it. I'm not sure how that's going to affect the new Debian source > format, but the upstreams that have picked up LZMA are already switching > to XZ. Interesting, hadn't heard about XZ. > There are a few CPAN modules that use .zip and the debian-perl group > standardizes watch patterns in part because it makes automated processing > easier. I don't think it makes sense for Lintian to be that picky, > though, since if one has more knowledge about a particular upstream, one > can rule out a lot of those extensions. (*.zip distributions, for > example, are usually because the upstream for that Perl module uses > Windows exclusively.) Hmmm, OK. -- bye, pabs http://wiki.debian.org/PaulWise
Attachment:
signature.asc
Description: This is a digitally signed message part