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

dealing with non-standard upstream packaging?


I was wondering if there is any info about best practice in the
situation where upstream source packaging doesn't use the standard
foo-0.1.2/ inside of foo-0.1.2.tar.gz scheme?

I suppose repacking the tarball/etc before using dh_make is enough, but
is there a standard way to make this a bit more automated for new
upstream releases?

Another, question: why do some orig.tar.gz files contain a tarball that
looks to be the upstream source, instead of being a copy of the upstream
source? gaim for example.


Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: