* Re: [beagleboard] Re: Beagle actions for Rev C validation software image [not found] ` <A69FA2915331DC488A831521EAE36FE4012470D042@dlee06.ent.ti.com> @ 2009-01-27 18:19 ` Jason Kridner 2009-01-27 21:02 ` Denys Dmytriyenko 0 siblings, 1 reply; 5+ messages in thread From: Jason Kridner @ 2009-01-27 18:19 UTC (permalink / raw) To: beagleboard, Openembedded-devel Adding oe-dev mailing list... On Tue, Jan 27, 2009 at 12:10 PM, Dmytriyenko, Denys <denys@ti.com> wrote: > >>> It's a bit sad that we're going to miss out on NEON and vo_omapfb by >>> going armv5te :( > >> Koen, > >> I am rebuilding 'mplayer' now with 'MACHINE=beagleboard bitbake mplayer', so that concern should go away. It shouldn't matter much about this mplayer, since it should only be used to test the hardware. > >> Can you consider inclusion of: > >> mplayer and FFmpeg dependency changes: >> http://www.beagleboard.org/gitweb/?p=arago-oe.git;a=commitdiff_plain;h=0b53219005c8daa95bcff40742d7c807bda17eca > > Hmm, I like these curl-inspired *_FEATURES handlers. The only problem with those is they won't trigger automatic rebuild when the featureset in the variable changes - don't forget to run bitbake -c rebuild manually... > Can I get a few comments on [1]? I found there is also a dependency in libtheora on x11 that doesn't seem necessary. I find this very useful to avoid making a new recipe. Anyone have ideas to address Denys' concern about needing to issue 'bitbake -c rebuild'? [1] http://www.beagleboard.org/gitweb/?p=arago-oe.git;a=commitdiff_plain;h=0b53219005c8daa95bcff40742d7c807bda17eca ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [beagleboard] Re: Beagle actions for Rev C validation software image 2009-01-27 18:19 ` [beagleboard] Re: Beagle actions for Rev C validation software image Jason Kridner @ 2009-01-27 21:02 ` Denys Dmytriyenko 2009-01-27 21:48 ` Koen Kooi 0 siblings, 1 reply; 5+ messages in thread From: Denys Dmytriyenko @ 2009-01-27 21:02 UTC (permalink / raw) To: openembedded-devel; +Cc: beagleboard On Tue, Jan 27, 2009 at 12:19:36PM -0600, Jason Kridner wrote: > Adding oe-dev mailing list... > > On Tue, Jan 27, 2009 at 12:10 PM, Dmytriyenko, Denys <denys@ti.com> wrote: > > > >>> It's a bit sad that we're going to miss out on NEON and vo_omapfb by > >>> going armv5te :( > > > >> Koen, > > > >> I am rebuilding 'mplayer' now with 'MACHINE=beagleboard bitbake mplayer', > >> so that concern should go away. It shouldn't matter much about this > >> mplayer, since it should only be used to test the hardware. > > > >> Can you consider inclusion of: > > > >> mplayer and FFmpeg dependency changes: > >> http://www.beagleboard.org/gitweb/?p=arago-oe.git;a=commitdiff_plain;h=0b53219005c8daa95bcff40742d7c807bda17eca > > > > Hmm, I like these curl-inspired *_FEATURES handlers. The only problem with > > those is they won't trigger automatic rebuild when the featureset in the > > variable changes - don't forget to run bitbake -c rebuild manually... > > Can I get a few comments on [1]? I found there is also a dependency > in libtheora on x11 that doesn't seem necessary. I find this very > useful to avoid making a new recipe. Anyone have ideas to address > Denys' concern about needing to issue 'bitbake -c rebuild'? > > [1] http://www.beagleboard.org/gitweb/?p=arago-oe.git;a=commitdiff_plain;h=0b53219005c8daa95bcff40742d7c807bda17eca For some reason Koen's reply never made it to the oe-dev list... Sorry for copying it here to continue the discussion. Koen said: > I'm against adding such 'USE flags' to OE, they basically make QA impossible. > If people want a different mplayer, they are free to make an 'mplayer-nox' or > 'mplayer-nosdl' recipe to fill their needs. But on the other hand it would make overlays, such as Arago, as well as OE itself, much cleaner and reduce the recipe creep. As of the rebuild issue when featureset in the variable changes, I was thinking about storing a hash of variable's value, in addition to the standard version and revision numbers, should trigger an automatic rebuild. Similar to bumping up a PR, but without modifying the recipe. Any thoughts? -- Denys ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [beagleboard] Re: Beagle actions for Rev C validation software image 2009-01-27 21:02 ` Denys Dmytriyenko @ 2009-01-27 21:48 ` Koen Kooi 2009-01-27 21:54 ` Jason Kridner 0 siblings, 1 reply; 5+ messages in thread From: Koen Kooi @ 2009-01-27 21:48 UTC (permalink / raw) To: openembedded-devel On 27-01-09 22:02, Denys Dmytriyenko wrote: > On Tue, Jan 27, 2009 at 12:19:36PM -0600, Jason Kridner wrote: >> Adding oe-dev mailing list... >> >> On Tue, Jan 27, 2009 at 12:10 PM, Dmytriyenko, Denys<denys@ti.com> wrote: >>>>> It's a bit sad that we're going to miss out on NEON and vo_omapfb by >>>>> going armv5te :( >>>> Koen, >>>> I am rebuilding 'mplayer' now with 'MACHINE=beagleboard bitbake mplayer', >>>> so that concern should go away. It shouldn't matter much about this >>>> mplayer, since it should only be used to test the hardware. >>>> Can you consider inclusion of: >>>> mplayer and FFmpeg dependency changes: >>>> http://www.beagleboard.org/gitweb/?p=arago-oe.git;a=commitdiff_plain;h=0b53219005c8daa95bcff40742d7c807bda17eca >>> Hmm, I like these curl-inspired *_FEATURES handlers. The only problem with >>> those is they won't trigger automatic rebuild when the featureset in the >>> variable changes - don't forget to run bitbake -c rebuild manually... >> Can I get a few comments on [1]? I found there is also a dependency >> in libtheora on x11 that doesn't seem necessary. I find this very >> useful to avoid making a new recipe. Anyone have ideas to address >> Denys' concern about needing to issue 'bitbake -c rebuild'? >> >> [1] http://www.beagleboard.org/gitweb/?p=arago-oe.git;a=commitdiff_plain;h=0b53219005c8daa95bcff40742d7c807bda17eca > > For some reason Koen's reply never made it to the oe-dev list... Sorry for > copying it here to continue the discussion. > > Koen said: >> I'm against adding such 'USE flags' to OE, they basically make QA impossible. >> If people want a different mplayer, they are free to make an 'mplayer-nox' or >> 'mplayer-nosdl' recipe to fill their needs. > > But on the other hand it would make overlays, such as Arago, as well as OE > itself, much cleaner and reduce the recipe creep. > > As of the rebuild issue when featureset in the variable changes, I was > thinking about storing a hash of variable's value, in addition to the > standard version and revision numbers, should trigger an automatic rebuild. > Similar to bumping up a PR, but without modifying the recipe. Any thoughts? I'm concerned with mplayer_1.0_armv7a.ipk not being the same as mplayer_1.0_armv7a.ipk, which is what USE flags do. regards, Koen ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [beagleboard] Re: Beagle actions for Rev C validation software image 2009-01-27 21:48 ` Koen Kooi @ 2009-01-27 21:54 ` Jason Kridner [not found] ` <E9998B7D-F3BE-484A-BDAE-75B25BEEC330@beagleboard.org> 0 siblings, 1 reply; 5+ messages in thread From: Jason Kridner @ 2009-01-27 21:54 UTC (permalink / raw) To: openembedded-devel, discussion On Tue, Jan 27, 2009 at 3:48 PM, Koen Kooi <k.kooi@student.utwente.nl> wrote: > On 27-01-09 22:02, Denys Dmytriyenko wrote: >> >> On Tue, Jan 27, 2009 at 12:19:36PM -0600, Jason Kridner wrote: >>> >>> Adding oe-dev mailing list... >>> >>> On Tue, Jan 27, 2009 at 12:10 PM, Dmytriyenko, Denys<denys@ti.com> >>> wrote: >>>>>> >>>>>> It's a bit sad that we're going to miss out on NEON and vo_omapfb by >>>>>> going armv5te :( >>>>> >>>>> Koen, >>>>> I am rebuilding 'mplayer' now with 'MACHINE=beagleboard bitbake >>>>> mplayer', >>>>> so that concern should go away. It shouldn't matter much about this >>>>> mplayer, since it should only be used to test the hardware. >>>>> Can you consider inclusion of: >>>>> mplayer and FFmpeg dependency changes: >>>>> >>>>> http://www.beagleboard.org/gitweb/?p=arago-oe.git;a=commitdiff_plain;h=0b53219005c8daa95bcff40742d7c807bda17eca >>>> >>>> Hmm, I like these curl-inspired *_FEATURES handlers. The only problem >>>> with >>>> those is they won't trigger automatic rebuild when the featureset in the >>>> variable changes - don't forget to run bitbake -c rebuild manually... >>> >>> Can I get a few comments on [1]? I found there is also a dependency >>> in libtheora on x11 that doesn't seem necessary. I find this very >>> useful to avoid making a new recipe. Anyone have ideas to address >>> Denys' concern about needing to issue 'bitbake -c rebuild'? >>> >>> [1] >>> http://www.beagleboard.org/gitweb/?p=arago-oe.git;a=commitdiff_plain;h=0b53219005c8daa95bcff40742d7c807bda17eca >> >> For some reason Koen's reply never made it to the oe-dev list... Sorry for >> copying it here to continue the discussion. >> >> Koen said: >>> >>> I'm against adding such 'USE flags' to OE, they basically make QA >>> impossible. >>> If people want a different mplayer, they are free to make an >>> 'mplayer-nox' or >>> 'mplayer-nosdl' recipe to fill their needs. >> >> But on the other hand it would make overlays, such as Arago, as well as OE >> itself, much cleaner and reduce the recipe creep. >> >> As of the rebuild issue when featureset in the variable changes, I was >> thinking about storing a hash of variable's value, in addition to the >> standard version and revision numbers, should trigger an automatic >> rebuild. >> Similar to bumping up a PR, but without modifying the recipe. Any >> thoughts? > > I'm concerned with mplayer_1.0_armv7a.ipk not being the same as > mplayer_1.0_armv7a.ipk, which is what USE flags do. Is it possible in OE to generate an ipk file name that gives some indication of the USE flags? Perhaps the right way to do this is with a common .inc file to avoid maintenance issues. ^ permalink raw reply [flat|nested] 5+ messages in thread
[parent not found: <E9998B7D-F3BE-484A-BDAE-75B25BEEC330@beagleboard.org>]
* Re: [beagleboard] Re: Beagle actions for Rev C validation software image [not found] ` <E9998B7D-F3BE-484A-BDAE-75B25BEEC330@beagleboard.org> @ 2009-01-27 22:25 ` Jason Kridner 0 siblings, 0 replies; 5+ messages in thread From: Jason Kridner @ 2009-01-27 22:25 UTC (permalink / raw) To: beagleboard, openembedded-devel On Tue, Jan 27, 2009 at 3:55 PM, Koen Kooi <koen@beagleboard.org> wrote: > > Op 27 jan 2009, om 22:54 heeft Jason Kridner het volgende geschreven: > >> >> On Tue, Jan 27, 2009 at 3:48 PM, Koen Kooi <k.kooi@student.utwente.nl> >> wrote: >>> >>> On 27-01-09 22:02, Denys Dmytriyenko wrote: >>>> >>>> On Tue, Jan 27, 2009 at 12:19:36PM -0600, Jason Kridner wrote: >>>>> >>>>> Adding oe-dev mailing list... >>>>> >>>>> On Tue, Jan 27, 2009 at 12:10 PM, Dmytriyenko, Denys<denys@ti.com> >>>>> wrote: >>>>>>>> >>>>>>>> It's a bit sad that we're going to miss out on NEON and vo_omapfb by >>>>>>>> going armv5te :( >>>>>>> >>>>>>> Koen, >>>>>>> I am rebuilding 'mplayer' now with 'MACHINE=beagleboard bitbake >>>>>>> mplayer', >>>>>>> so that concern should go away. It shouldn't matter much about this >>>>>>> mplayer, since it should only be used to test the hardware. >>>>>>> Can you consider inclusion of: >>>>>>> mplayer and FFmpeg dependency changes: >>>>>>> >>>>>>> >>>>>>> http://www.beagleboard.org/gitweb/?p=arago-oe.git;a=commitdiff_plain;h=0b53219005c8daa95bcff40742d7c807bda17eca >>>>>> >>>>>> Hmm, I like these curl-inspired *_FEATURES handlers. The only problem >>>>>> with >>>>>> those is they won't trigger automatic rebuild when the featureset in >>>>>> the >>>>>> variable changes - don't forget to run bitbake -c rebuild manually... >>>>> >>>>> Can I get a few comments on [1]? I found there is also a dependency >>>>> in libtheora on x11 that doesn't seem necessary. I find this very >>>>> useful to avoid making a new recipe. Anyone have ideas to address >>>>> Denys' concern about needing to issue 'bitbake -c rebuild'? >>>>> >>>>> [1] >>>>> >>>>> http://www.beagleboard.org/gitweb/?p=arago-oe.git;a=commitdiff_plain;h=0b53219005c8daa95bcff40742d7c807bda17eca >>>> >>>> For some reason Koen's reply never made it to the oe-dev list... Sorry >>>> for >>>> copying it here to continue the discussion. >>>> >>>> Koen said: >>>>> >>>>> I'm against adding such 'USE flags' to OE, they basically make QA >>>>> impossible. >>>>> If people want a different mplayer, they are free to make an >>>>> 'mplayer-nox' or >>>>> 'mplayer-nosdl' recipe to fill their needs. >>>> >>>> But on the other hand it would make overlays, such as Arago, as well as >>>> OE >>>> itself, much cleaner and reduce the recipe creep. >>>> >>>> As of the rebuild issue when featureset in the variable changes, I was >>>> thinking about storing a hash of variable's value, in addition to the >>>> standard version and revision numbers, should trigger an automatic >>>> rebuild. >>>> Similar to bumping up a PR, but without modifying the recipe. Any >>>> thoughts? >>> >>> I'm concerned with mplayer_1.0_armv7a.ipk not being the same as >>> mplayer_1.0_armv7a.ipk, which is what USE flags do. >> >> Is it possible in OE to generate an ipk file name that gives some >> indication of the USE flags? Perhaps the right way to do this is with >> a common .inc file to avoid maintenance issues. > > If it magically mangles package names, what's so different from creating > multiple recipes? I think the differences are the names being sensible (based on having multiple recipes and using a .inc file to avoid maintenance issues) vs. maintaining fewer recipes. The USE flags also give greater flexibility at the distribution level, but I've only seen a limited number of cases for which this is currently required. As long as the recipes give ?= assignments, "personal" distributions could still be generated at the local.conf level. The idea to add a hash to trigger an automatic rebuild if relevant USE flags change still seems quite useful (and even putting the USE flags into the control file). ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2009-01-27 22:33 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <5899DAF1-278D-43D5-8C90-BECD7FC3E4B5@beagleboard.org>
[not found] ` <f20732e90901270708t65dc4a67jfe0829bb6ca4c540@mail.gmail.com>
[not found] ` <B1B8AC48-51AB-435E-A431-AC1494B171DA@beagleboard.org>
[not found] ` <670B7A54-3C74-42FD-A6F8-DAAFD4AEC73A@beagleboard.org>
[not found] ` <A69FA2915331DC488A831521EAE36FE4012470D042@dlee06.ent.ti.com>
2009-01-27 18:19 ` [beagleboard] Re: Beagle actions for Rev C validation software image Jason Kridner
2009-01-27 21:02 ` Denys Dmytriyenko
2009-01-27 21:48 ` Koen Kooi
2009-01-27 21:54 ` Jason Kridner
[not found] ` <E9998B7D-F3BE-484A-BDAE-75B25BEEC330@beagleboard.org>
2009-01-27 22:25 ` Jason Kridner
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.