SRCREV and git packages

[Werner Almesberger]

Holger Freyther wrote:
> You will need a local repository for every piece of git software we use, even 
> if you don't use it at all. E.g. three disjunct kernel trees wasting some 
> harddisk space.

Hmm, why ? What is the operation that actually requires you to compare
versions ?

If it's just things like "package foo requires libbar >= 10", then the
it should be easy:

- if we don't have any version of libbar yet, we fetch it

- if we have some version of libbar, we've had at some point in time
  access to the repository, and could thus have obtained the sequential
  number.

  So the question is reduced to "how to we make sure the number is
  still around" ?
  
If the query is "package furble requires libgoo >= hash:0e4a83f...",
that information is harder to obtain. One would basically need the
repository at the time of making the package. Still, this would now
be a problem for the package maker (or one entity in the chain that
leads to publishing the package), not the end-user.

Queries like "give me the latest libbaz" should also be easy to answer:

- if there is no libbaz installed, we fetch it

- if it is installed, we can already know all its version numbers, so
  it's just a question of putting them all together

Am I missing something ?

- Werner