Hi Jessica,
Yes it makes sense.
The reason why I started refactoring the code in the remote tools is to try and
isolate the functionality we need to move to the separate plugin. Instead of
moving everything in the first place, I am trying to reduce the code to single
points of control
rpi-first-run-wizard depends on zenity, which is in meta-gnome.
However the README file for meta-raspberrypi says only oe-core and
meta-oe layers are required (lines 105 and 106 of the current README).
I'd say the 2 possible solutions are either listing meta-gnome as a
layer dependency or
Hello,
Sometimes I feel the need to clean everything before building, but I don't want
to just rm my project directory since I want to keep my conf files. What
bitbake command can I run to get back to a pristine state (same as
after creating project directory and modifying my conf
On Apr 27, 2013, at 9:30 AM, Peter Tornel petertor...@yahoo.com wrote:
Hello,
Sometimes I feel the need to clean everything before building, but I don't
want to just rm my project directory since I want to keep my conf files.
What bitbake command can I run to get back to a
On 27 April 2013 18:21, Khem Raj raj.k...@gmail.com wrote:
rm -rf tmp/
configurations are kept outside. tmp/
You may also need to get rid of 'pseudodone' (as pseudo is kept under
'tmp' and will need rebuilding), 'cache' and 'sstate-cache'.
--
Paul Barker
Email: p...@paulbarker.me.uk
Hi Ioana,
OK, then can you resend the patch set and drop the first patch so that the
patch set is clearer on what they're meant to be? E.g. in this case, cleanup
the remote tools function usage. Btw, will the 3 patches all you'll need for
cleanup or there'll be more? If there'll be more,
Merged into eflanagan/yocto-autobuilder-refactor. Will deploy to
production this week. Thanks!
-b
On Wed, Apr 24, 2013 at 3:29 PM, Stefan Stanacar
stefanx.stana...@intel.com wrote:
Hello Beth,
Here are the new changes, I've fixed that small issue, hope it looks good now.
After some more
This mail was sent out by Package Report System.
This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade this time, they can fill in
RECIPE_NO_UPDATE_REASON_pn-xxx in upstream_tracking files to ignore this
recipe remainder until newer
This mail was sent out by Package Report System.
It will list all the recipes which can't check upstream version by script, and
will show how long it is since their last mannual version check.
You can check the detail information at
http://packages.yoctoproject.org/manuallychkinfo
PackageName
