Am Freitag, den 28.07.2006, 18:25 +0100 schrieb Richard Purdie:
> On Fri, 2006-07-28 at 17:58 +0200, Michael 'Mickey' Lauer wrote:
> > Am Mittwoch, den 26.07.2006, 23:01 +0100 schrieb Richard Purdie:
> > > On Sun, 2006-07-02 at 17:36 +0200, freyther commit wrote:
> > > > --- classes/opie.bbclass 56f1af0d33515f3ce406525592cdadcec86715c4
> > > > +++ classes/opie.bbclass a521ba92e8eb0138c562fa0a36a90e8998aa8f3e
> > > > @@ -18,7 +18,7 @@
> > > > # Note that when CVS changes to 1.2.2, the dash
> > > > # should be removed from OPIE_CVS_PV to convert
> > > > # to the standardised version format
> > > > -OPIE_CVS_PV = "1.2.1+cvs-${SRCDATE}"
> > > > +OPIE_CVS_PV = "1.2.2+cvs-${SRCDATE}"
> >
> > What "standard" is this talking about anyway? :D
> >
> > Seriously, I can't remember we agreed on one.
>
> http://www.openembedded.org/wiki/VersioningPolicy ?
Ah right. Excellent. I promise to remember when Opie 1.2.3 is due
(somewhere in winter).
> Thinking of policies, I'd still like to see a preferred ordering of
> variables added to the style guide on the wiki. I think you mentioned
> you have an order you wanted to suggest?
Yeah, my idea is roughly based on a HEADER/BODY/FOOTER partitioning and
the natural flow as tasks are processing the metadata. I have added my
recommendation to http://www.openembedded.org/wiki/StyleGuide
I can enhance it, if you think it's too brief.
Thinking about it, it would be cool to have a tool that could use the
high level model of the metadata in a .bb to transform .bb files into a
canonical style. Beyond the equation there are a lot of statements that
are based on order though, so I don't think it would be very easy.
--
Regards,
Michael 'Mickey' Lauer | FreeLancer | http://www.Vanille-Media.de
_______________________________________________
Oe mailing list
[email protected]
https://www.handhelds.org/mailman/listinfo/oe
