[Rock-dev] [rock] #426: autoproj does not install osdep on its own

[rock]

#426: autoproj does not install osdep on its own
-----------------------+---------------------
Reporter: jama01 | Owner: sjoyeux
Type: defect | Status: new
Priority: normal | Milestone:
Component: toolchain | Keywords:
-----------------------+---------------------
Something is weired with the osdeps tracking.
It seems amake does not check for OS-Deps first.
Using autoproj osdeps manually works fine btw.
Error case is attached

[rock]

#426: autoproj does not install osdep on its own
-----------------------+----------------------
Reporter: jama01 | Owner: sjoyeux
Type: defect | Status: new
Priority: normal | Milestone:
Component: toolchain | Resolution:
Keywords: |
-----------------------+----------------------

Comment (by sylvain.joyeux):

amake is not supposed to run the osdeps. However, aup should have. Since
it is so long ago I guess we won't know what really happened :( Sorry

[rock]

#426: autoproj does not install osdep on its own
-----------------------+----------------------
Reporter: jama01 | Owner: sjoyeux
Type: defect | Status: new
Priority: normal | Milestone:
Component: toolchain | Resolution:
Keywords: |
-----------------------+----------------------

Comment (by mago02):

I know (and see this point), i had somethims simliar things.

If you not have any package so far installed autoproj build will download
and install it.
But then no osdeps are triggered.

Other example is if the user aborts the update (because he maybe dont want
to get core-packages updates), the osdeps is not triggered too.

We should thing about installing osdeps for packages thare are build the
first time (e.g don't have a build folder so far?!).

[rock]

#426: autoproj does not install osdep on its own
--------------------+----------------------
Reporter: jama01 | Owner: sjoyeux
Type: defect | Status: new
Priority: major | Milestone:
Component: base | Resolution:
Keywords: |
--------------------+----------------------
Changes (by sylvain.joyeux):

* priority: normal => major
* component: toolchain => base

Post by rock
Other example is if the user aborts the update (because he maybe dont

want to get core-packages updates), the osdeps is not triggered too.
Sorry, but no way that I'm targetting this particular workflow ... If you
CTRL+C, you CTRL+C. Period. Fixing package pinning is another story.

Post by rock
We should thing about installing osdeps for packages thare are build the

first time (e.g don't have a build folder so far?!).
I'll have a look. We should definitely be able to run an autoproj update
stage for all non-currently-checked-out packages.