[oe] The future of "svnnow"

[Koen Kooi]

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

Richard Purdie schreef:

> 
> What still needs to be done (patches welcome)
> =============================================
> 
> 1. Fix revision lockdown SRCREV_pn-somepackage = "90" etc. Thats a
> problem in localpath() in svn.py.
> 
> 2. Handling of multiple SCMs in the SRC_URI. The plan here is simple,
> any package doing this has to set SRCREV_FORMAT specifying the format of
> the SRCREV string. get_srcrev() can collect the SCM revisions, fill out
> the string and return it. The format and inner workings of this are open
> for discussion and to be determined. 
> 
> 3. Finish sortable_revision(). If self._sortable_revision() isn't
> present, it should read a counter, revision pair from BB_URI_LOCALCOUNT.
> If the revision is different to _latest_revision, increase the counter
> and store + return it. 
> 
> 4. Fix the git fetcher to make git "now" work. These "local revision
> counter" packages will not be shareable between different builds but we
> always knew that would be the case with git and this is as close as we
> can get.
> 
> 5. Examine the other fetchers and see if we can add some kind of "now"
> support to them too.
> 
> 6. Add policy control variables to control the wiping of BB_URI_HEADREVS

  7. make a minrev and max rev for patches and try to convert dates to revisions for
existing users of ;mindate=20070707;maxdate=20080808 in SRC_URI

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFGrumgMkyGM64RGpERAvY+AJwIksReey1LVHa6NpFRvcdFvldPOgCfbeLO
jvrr6XXcdJFxRjH+GFUsQlU=
=9FHq
-----END PGP SIGNATURE-----