Re: Improvements to ‘debian/watch’ for fetching from VCS
On Thu, Apr 02 2009, Noah Slater wrote:
> On Fri, Apr 03, 2009 at 10:50:11AM +1100, Ben Finney wrote:
>> That's the trouble though. AIUI, different VCSen have different ways
>> of identifying a specific state of the working tree; we have not only
>> revisions, but also tags, branches, threads, heads, and probably
>> others I've forgotten. Should all of those be allowed? Is that too
>> complex an interface?
>> As for “latest”: is there an unambiguous “latest” for every
>> repository? What does this mean with repositories that have
>> simultaneous lines of history within the same location?
> Okay, but for the purposes of this file we only need two actions, right? Is the
> current version the latest one we're interested in, and how can we fetch the
> upstream source for the current version. If we let these two actions be scripted
> through a standard interface, it should work with any repository.
If the current version is what we are interested, why not get it
from the canonical site, the Debian archive?
I am not seeing the sue case for not getting the sources
distributed by Debian from Debian. People who do not trust the Debian
archive, ought not to trust the Debian script, and go get the upstream
using a trusted download agent on their own; so security is not the use
By far the most common use case I can see is to get the latest
upstream, and do whatver munging needs to be done to make it acceptable
for Debian as a source archive.
What am I missing?
Moore's Constant: Everybody sets out to do something, and everybody does
something, but no one does what he sets out to do.
Manoj Srivastava <firstname.lastname@example.org> <http://www.debian.org/~srivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C