SRCREV and git packages

Andy Green andy at openmoko.com
Wed Jun 4 18:35:01 CEST 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Somebody in the thread at some point said:
| On Wednesday 04 June 2008 16:52:52 Andy Green wrote:
|> Somebody in the thread at some point said:
|> | Holger Freyther wrote:
|> |> To be able to upgrade you need to have increasing version numbers.
With
|> |> subversion this is trivial, with a hash (as provided by git) this not
|> |> trivial. A more recent kernel might have a hash that is smaller
than the
|> |> month old one.
|> |
|> | Yup, I understand that. But, assuming you've already installed package
|> | foo, version X, then the question in your example is "is there a more
|> | recent version of foo than version X".
|>
|> Isn't this an issue because only we don't generate source packages, you
|> need a magic tag to go to in the scm to recover the sources
|> corresponding to the binary package?
|
| Hey Andy,
|
| this is getting really boring. You have made your point, cope with
that. I
| don't tell you how you should do your work either. The "lack" of a source

Actually you do, but never mind.  Maybe it's boring for you because you
didn't understand my point.

There are two separate things being talked about, I was responding to
what Werner wrote:

| Yup, I understand that. But, assuming you've already installed package
| foo, version X, then the question in your example is "is there a more
| recent version of foo than version X".

The answer to that is indeed "was a later version built", and you could
rejig around that with a built host tag in the package name.


The question about source capture was triggered by you wrote on the
kernel list about this system being unable to deal with git history
rewriting:

''please only use fast-forward commits (no git-push --force) for the
stable branch. Not doing this will create an issue for our autobuilders.

We have this issue. If we build a specific revision which gets
"orphaned" (no one is referencing is) and people do a fresh
checkout/clone they will not get this revision or with a git-gc this
revision will be garbage collected.''

Doesn't this have ramifications for source capture, or is it about
something else:  ''If we *build* a specific revision which gets
"orphaned" (no one is referencing is) and people do a fresh
checkout/clone they will not get this revision''?  If so, a source
package a build time would indeed resolve it.  Right?

- -Andy

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkhGxDUACgkQOjLpvpq7dMrxqwCgiVqkx0resI2OLTo3SvohRKyP
UFwAniYgv+STPJ6AuJDg1HHQeFrs8k14
=wJon
-----END PGP SIGNATURE-----



More information about the distro-devel mailing list