[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]



I was playing around with cvs-buildpackage today (*very* slick set of tools,
I'm going to send Manoj a thank you note for this one. Heck, if I lived
anywhere near him, I'd pay him a <insert Manoj's beverage of choice here>
:-) ), and noticed that my source .orig.tar.gz were a bit bogus:
foo_1.2.3.orig.tar.gz was unpacking itself into foo-1.2.3, instead of
foo-1.2.3.orig as the packaging manual requires.

However, dpkg-source and lintian were perfectly happy with the broken
.orig.tar.gz files, which is the reason I hadn't noticed my mistake until I
looked at the orig.tar.gz created by cvs-buildpackage and looked it up in
the packaging manual.

Should I be filling a wishlist bug against lintian, or is it ok (although
not optimal) to have .orig.tar.gz files unpacking at foo-1.2.3 instead of
foo-1.2.3.orig ?

  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

Attachment: pgpmJL4dXbY5H.pgp
Description: PGP signature

Reply to: