Re: Bug#466550: Please clarify the get-orig-source target stated in Policy 4.9
Am Dienstag, den 19.02.2008, 15:16 +0100 schrieb Alexander Schmehl:
> Package: debian-policy
> Version: 18.104.22.168
> Severity: wishlist
> X-Debbugs-CC: email@example.com, firstname.lastname@example.org
> Dear policy team,
> recently the get-orig-source target of debian/rules has been discussed
> on the debian-mentors list (see the threads starting with  and ).
> It seems the get-orig-source specific paragraph of section 4.9 should be
> improved to a bit more clearly and answer some open questions, too.
> Basically it boils down to two or three open questions:
> The first one being, if get-orig-source is intendedn to fetches the most
> recent version of the original source upstream wise or if it should
> fetch the most recent version debian wise.
That should be done by uscan invoking "debian/rules get-orig-source" as
suggested several times. This won't make the situation more complicated.
It just requires that any variables necessary to create the tarball
(e.g. upstream version, svn version number, ...) can be overwritten by
uscan (already explained it in this thread)
> If the later is the case and of a package has a version in
> experimentatl, should get-orig-source fetch the version of experimental
> or from unstable?
It should IMO fetch the version by parsing debian/changelog. That's
simple and logical. uscan can overwrite these variables.
> And last questions: Where should tools used in get-orig-source (e.g.
> bzip2 or unzip to repacke a tarball) be declared? As Build-Dependency?
> Anywhere else?
I don't think, they should be declared in Build-Depends, because they
are simply not necessary to build the package. No target in debian/rules
invokes get-orig-source during a build and people invoking this target
should be able to check debian/rules, if something goes wrong. But to be
honest: This target normally requires only bzip2/gzip/tar, wget (maybe
we can drop this, if uscan invokes get-orig-source) and rm + sometimes