Re: Writing get-orig-source targets to conform with policy
Am Samstag, den 16.02.2008, 23:10 -0500 schrieb Andres Mejia:
> I have two questions. First question is;
> Is it at all possible to write a get-orig-source target that calls an external
> script to handle generating the orig tarball?
> The problem I'm facing is when the get-orig-source target is written like:
> It works fine under the package's top directory, but fails under any other
> directory, for instance, /tmp. I've looked over the GNU make documentation
> hoping to find a special parameter for finding the name of the make script
> ran, just how a shell script has "$0", but I've been unable to find one.
Work in the current directory or in /tmp using mktemp. I have written
get-orig-source targets for almost all docbook* packages  I maintain
(where uscan isn't enough). Maybe they are useful examples.
> Second question is regarding a get-orig-source target I have for the package
> mediatomb. It goes like:
> # Common variables used to ease maintenance of the get-orig-source target.
> MEDIATOMB_TARBALL = mediatomb-0.10.0.tar.gz
> MEDIATOMB_VERSION = 0.10.0
> CORRECT_CHECKSUM = 2436c73de4ac5f3ba1575f7ee93a0430
> # Haven't found a way to use this without running it twice
> COMPUTED_CHECKSUM = $(shell md5sum $(MEDIATOMB_TARBALL) | cut -d ' ' -f 1)
> [ -e $(MEDIATOMB_TARBALL) ] || \
> wget http://downloads.sourceforge.net/mediatomb/$(MEDIATOMB_TARBALL)
The checksum is computed before you download the tarball. Compute it
after this step.
(docbook, d-xml, d-xsl, d-xsl-saxon, d-simple, d-ebnf, d-defguide)