[oe] RFC: reverse the name change for org.oe.stable

[Holger Freyther]

On Monday 12 May 2008 09:19:21 Richard Purdie wrote:
> On Mon, 2008-05-12 at 00:46 +0200, Leon Woestenberg wrote:
> > Yes, do not use _<scm> recipes in stable stuff, a known checkout of
> > the OE stable branch should either build or not for a particular
> > machine/distro/... combo.
> >
> > If I checkout today's stable tree in one year time, it should build.
> > Period.
> >
> > That isn't going to work with _<scm> recipes being active in stable.
>
> Floating SCM versions won't be reproducible, fixed SCM versions will. If
> SCM versions are used they need to be locked to a version.

The reality is that SRCDATE is completely meaningless for at least CVS and 
SVN. Even worse with CVS and SVN the history can be altered and even if you 
checkout e.g. the glibc repo by date you get a different snapshot that you 
got last time you tried.

The sad reality is that only SCMs with a hash as revision number can be 
trusted, for the others we would have to make sure that the mirrors carry the 
checkout as we used it to build the package and to disable checking stuff out 
by date/revnumber in bitbake for a real stable branch.


just my two cents, I might be off topic.
	z.