Proper way to update pybombs

How can I update pybombs (to get the latest version and update the
recipes) without loosing the information about my gnuradio build? I want
to continue to update gnuradio without the need to do a complete rebuild
after a pybombs update.
tnx, Mark

On 09/14/2013 06:01 AM, M Dammer wrote:

How can I update pybombs (to get the latest version and update the
recipes) without loosing the information about my gnuradio build?
in your pybombs directory or pybombs recipe directory run

git remote update
git pull

this should pull down any pybombs updates that may be available
you may want to ‘git stash’ before pulling and ‘git stash pop’ after if
you have any local changes.
or merge with a local branch with local modifications if you know what
you are doing

I want
to continue to update gnuradio without the need to do a complete rebuild
after a pybombs update.
The ‘safe’ way to rebuild updated modules is to run
./pybombs update
this will

  1. find any out of date packages - and all packages that depend on these
  2. uninstall all of these packages for you
  3. perform a fresh install of all of these packages

this may seem like overkill - but it is the only truly safe way to
ensure
you can try the shortcut approach - which is to run

cd pybombs/src/gnuadio/
git remote update
git pull
cd build
make install

this is much much faster to do, it may not even need to run cmake if
changes were very minor
however - if you don’t rebuild everything that links against gnuradio
there is a danger that you will break linkage or some API/ABI contract
with the dependent library, and there is always a danger that cmake
won’t automatically re-generate some file that is is supposed to when
running this (like swig sources) - so when you do this you are rolling
the dice.
You may be able to get away with this a few times, but invariably one
day you will start running into strange seg-faults which seem
nonsensical, and which would completely go away in a fresh build.
The other safe thing is to just do a fresh pybombs build in a separate
directory so you don’t lose your old working build while testing against
the latest versions of code from various repos.

-Tim

On 14/09/13 15:30, Tim wrote:

you have any local changes.
or merge with a local branch with local modifications if you know what
you are doing

Thanks Tim for your detailed reply, but this does not work for me. I am
getting a lot of “conflict” messages like this:

CONFLICT (add/add): Merge conflict in RPCPybombs.ice
Auto-merging .bash_completion.d/pybombs
CONFLICT (add/add): Merge conflict in .bash_completion.d/pybombs
Automatic merge failed; fix conflicts and then commit the result.

and at the very end the pybombs file itself is corrupted. It looks like
the output of a “diff” merged with working python code. I think I am
going to rebuild everything … :frowning:

Mark

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs