| Submitter | Tom Zanussi |
|---|---|
| Date | June 14, 2011, 8:20 p.m. |
| Message ID | <1308082816.10825.38.camel@elmorro> |
| Download | mbox | patch |
| Permalink | /patch/5949/ |
| State | New, archived |
| Headers | show |
Comments
Op 14 jun 2011, om 22:20 heeft Tom Zanussi het volgende geschreven: > On Tue, 2011-06-14 at 00:40 -0700, Koen Kooi wrote: >> Op 13 jun 2011, om 23:30 heeft Richard Purdie het volgende geschreven: >> >>> On Mon, 2011-06-13 at 22:36 +0200, Koen Kooi wrote: >>>> Op 13 jun 2011, om 22:28 heeft Saul Wold het volgende geschreven: >>>> >>>>> On 06/13/2011 11:31 AM, Koen Kooi wrote: >>>>>> Hi, >>>>>> >>>>>> Khem was asking if I could reproduce the recent x86 breakage he was seeing[1] and I ran into another bug: >>>>>> >>>>>> koen@dominion:/OE/tentacle/sources/meta-intel$ git blame meta-n450/conf/machine/n450.conf | grep atom >>>>>> 158f88d7 (Saul Wold 2011-01-03 15:33:52 -0800 6) require conf/machine/atom-pc.conf >>>>>> >>>>> meta-yocto seems to be the place you need to look! >>>>> >>>>> I hope that the layering tools can help to detect and inform folks of this like of dependency. >>>> >>>> Isn't meta-yocto supposed to a the integration layer with no new >>>> parts? I can't use meta-yocto since it has conflicting beagleboard >>>> stuff in it, which means that meta-intel is now broken for me as well. >>>> That surely isn't the intended plan?!?! >>> >>> The plan on public record is that atom-pc moves to meta-intel as soon as >>> the layer tooling comes online and meta-yocto becomes its own repo >>> (which at present its not but its certainly the intent). >> >> So can someone at least put that in the meta-intel or meta-n450 README? Most layers now have a README with the dependency info (e.g. http://git.shr-project.org/git/?p=meta-smartphone.git;a=blob;f=meta-palm/README;h=200a3c83ff11ad790fe4e03e93a26520ec0c6714;hb=HEAD ) It would be nice if the ones on yocto-project.org had somethign similar :) >> _ > > Would something like this do the trick for now (if so, I can do similar > for the other meta-intel bsps)? I'd put it in README, but yeah, it's an improvement.
On Tue, 2011-06-14 at 14:08 -0700, Koen Kooi wrote: > Op 14 jun 2011, om 22:20 heeft Tom Zanussi het volgende geschreven: > > > On Tue, 2011-06-14 at 00:40 -0700, Koen Kooi wrote: > >> Op 13 jun 2011, om 23:30 heeft Richard Purdie het volgende geschreven: > >> > >>> On Mon, 2011-06-13 at 22:36 +0200, Koen Kooi wrote: > >>>> Op 13 jun 2011, om 22:28 heeft Saul Wold het volgende geschreven: > >>>> > >>>>> On 06/13/2011 11:31 AM, Koen Kooi wrote: > >>>>>> Hi, > >>>>>> > >>>>>> Khem was asking if I could reproduce the recent x86 breakage he was seeing[1] and I ran into another bug: > >>>>>> > >>>>>> koen@dominion:/OE/tentacle/sources/meta-intel$ git blame meta-n450/conf/machine/n450.conf | grep atom > >>>>>> 158f88d7 (Saul Wold 2011-01-03 15:33:52 -0800 6) require conf/machine/atom-pc.conf > >>>>>> > >>>>> meta-yocto seems to be the place you need to look! > >>>>> > >>>>> I hope that the layering tools can help to detect and inform folks of this like of dependency. > >>>> > >>>> Isn't meta-yocto supposed to a the integration layer with no new > >>>> parts? I can't use meta-yocto since it has conflicting beagleboard > >>>> stuff in it, which means that meta-intel is now broken for me as well. > >>>> That surely isn't the intended plan?!?! > >>> > >>> The plan on public record is that atom-pc moves to meta-intel as soon as > >>> the layer tooling comes online and meta-yocto becomes its own repo > >>> (which at present its not but its certainly the intent). > >> > >> So can someone at least put that in the meta-intel or meta-n450 README? Most layers now have a README with the dependency info (e.g. http://git.shr-project.org/git/?p=meta-smartphone.git;a=blob;f=meta-palm/README;h=200a3c83ff11ad790fe4e03e93a26520ec0c6714;hb=HEAD ) It would be nice if the ones on yocto-project.org had somethign similar :) > >> _ > > > > Would something like this do the trick for now (if so, I can do similar > > for the other meta-intel bsps)? > > I'd put it in README, but yeah, it's an improvement. OK, yeah, for some reason n450 decided to name its README 'ReleaseNotes'. I'll find out if there was a reason for that and rename it to README like the others if not... Tom > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Patch
diff --git a/meta-n450/ReleaseNotes b/meta-n450/ReleaseNotes index 23ac815..4257d94 100644 --- a/meta-n450/ReleaseNotes +++ b/meta-n450/ReleaseNotes @@ -1,8 +1,38 @@ Poky Laverne Release 4.0 +- Dependencies - Features and Updates - Known Issues +DEPENDENCIES +============ + +This layer depends on: + + URI: git://git.openembedded.org/bitbake + branch: master + + URI: git://git.openembedded.org/openembedded-core + layers: meta + branch: master + + URI: git://git.yoctoproject.org/poky + layers: meta-yocto + branch: master + +NOTE: n450 currently depends on meta-yocto due to atom-pc +dependencies. The plan is to move atom-pc to meta-intel as soon as +the layer tooling comes online and meta-yocto becomes its own repo. +At that point, meta-yocto will no longer be required. + +Note also that the layering with respect to the poky repo is in +transition; it currently contains both meta from openembedded-core and +bitbake along with some other files and directories which will +eventually be contained in standalone repos once the ongoing layering +work has been completed. As such, the master branch of the poky repo +can at the present time be used to satisfy all meta-intel +dependencies. + FEATURES AND UPDATES ====================