Re: Bug#466550: Pristine source from upstream VCS repository
[Moving this away from the BTS]
On Thu, Mar 12 2009, Steve Langasek wrote:
> On Thu, Mar 12, 2009 at 12:38:24PM -0500, Manoj Srivastava wrote:
>> Is this so very different from what people do? Some times I do
>> not package every upstream version, if they are coming in rapid
>> succession, or if I find some version unfit for Debian -- but in any
>> case, the majority of the time I want to package the very latest
>> upstream version.
> The difference is having a get-orig-source that works for the majority
> case (I want to package the very latest), instead of working for all
> cases (I want to package upstream version $x, which may or may not be
> the latest).
How do you propose that one specifies "get and munge the latest
source" when one might not know a priori what the version number might
be? The interface spec of this target that works for all cases is not
very clear to me. Does a missing verion mean I want the latest? Or that
I want to use the version in the Changelog? I had imagined that he
current language in policy that says get the /latest/ was at least
unambiguous on this, but I seem to have been in error.
Does it make sense to have more than one target? Should it be a
target in rules, as opposed to a script in ./debian? The advantage of a
separate script is hat it is easy to check if the script exists
(whether or not a Make target exists is hard to determine), and it is
easier to communicate options to a script.
I can see that we can have get-orig-source-latest and
get-orig-source-current scripts in ./debian, and would prefer that to
overloading a single make target, with all the hassles of assing
arguments in env variables.
Bye Bye PDP 10
Manoj Srivastava <email@example.com> <http://www.debian.org/~srivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C