recipe

I have a batch job that I need to run occasionally against my Plone instance. It needs access to the code in my Plone product and other Plone code and to query the catalog. I've included the script in my Plone product and currently run it via bin/instance run <path to script in eggs directory> Obviously if a new version of my product comes along I need to change the path to point to the new version of the egg. What I'd like to do is define any entry point for the script in my product's setup.py and then use the buildout recipe like zc.recipe.egg so that I can just run bin/myscript How do I do

This is the situation: We have a series of users who share some documents. The documents they can share might change throughout the day, so can the documents themselves (changes and deletions). The users can change some information on the documents. E.g. Users | Documents A | X A | Y A | Z B | X B | Z C | Y Possible groups: A+C, A+B The server on CouchDB is a replica of a SQL Server DB with this data, an ETL takes care of managing changes on CouchDB. However, the CouchDB database is replicated on each user phone via PouchDB. The goal: To replicate changes and deletions accordingly. What we've

I am trying to install the fog gem in a chef recipe though the gem installation occurs before the native packages are being installed so the gem installation fails package "libxslt-dev" package "libxml2-dev" chef_gem "fog" This is the output [Thu, 14 Mar 2013 13:04:30 +0000] INFO: Processing chef_gem[fog] action install (ebs4000::update_volumes line 23) [Thu, 14 Mar 2013 13:04:52 +0000] ERROR: Running exception handlers [Thu, 14 Mar 2013 13:04:52 +0000] FATAL: Saving node information to /var/cache/chef/failed-run-data.json [Thu, 14 Mar 2013 13:04:52 +0000] ERROR: Exception handlers complete

I would like to use a loop to find some files and rename them: for i in `find $@ -name *_cu.*`;do mv $i "$(echo $i|sed s/_cu//)" done This works in the shell. But how can I do this in a makefile recipe? There are two main things you need to know when putting non-trivial shell fragments into make recipes: Commands in the recipe are (of course!) executed one at a time, where command means "tab-prefixed line in the recipe", possibly spread over several makefile lines with backslashes. So your shell fragment has to be written all on one (possibly backslashed) line. Moreover it's effectively

I have a directory of 'binary' (i.e. not to be compiled) files and just want them to be installed onto my target root file system. I have looked at several articles, none of which seem to work for me. The desired functionality of this recipe is: myRecipe/myFiles/ --> myRootFs/dir/to/install My current attempt is: SRC_URI += "file://myDir" do_install() { install -d ${D}/path/to/dir/on/fs install -m ${WORKDIR}/myDir ${D}/path/to/dir/on/fs } I can't complain about the Yocto documentation overall, it's really good! Just can't find an example of something like this! You just have to copy these

I have a tarball src.tar.gz whose contents are unpacked into src/ and a patch of this sources generated with this command: $ diff -Nurp src/ src_mod/ > my.patch The patch header starts with this three lines: diff -Nurp src/path/to/file src_PATCHED/path/to/file --- src/path/to/file 2012-10-22 05:52:59.000000000 +0200 +++ src_PATCHED/path/to/file 2016-03-14 12:27:52.892802283 +0100 My bitbake recipe references both path and tarball files using this SRC_URI: SRC_URI = " \ file://my.patch \ file://src.tar.gz \ " do_fetch and do_unpack tasks work as expected, leaving my.patch and src/ inside ${S}