SRCREV and git packages
andy at openmoko.com
Wed Jun 4 16:52:52 CEST 2008
-----BEGIN PGP SIGNED MESSAGE-----
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?
If you did build source packages, you could forget this issue and
maintain an incrementing "release" index number that is per build host,
and a package tag identifying the build group. There is the solution
for detecting newer packages... and it seems the built host -scope
incrementing number is already an established practice anyway with this
r<number> in the package names if I understood it.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the distro-devel