[Rock-dev] Autoproj v2

[Sylvain Joyeux]

> Because I find it to be a robust, self sufficient and transparent
> process to start my installations.
> no need to look for an (potentially outdated) autoproj_install script.

First of all, any process that involves getting into a dot folder
manually is NOT transparent and self-sufficient. It's the equivalent
of using private APIs. You can't complain if it stops working.

If you don't download the script each time, you're doing something
wrong. I would have happily broken your "transparent install method"
and would not have apologized for it anytime. The only supported
bootstrap method is and has always been:

- [download the autoproj_install or autoproj_bootstrap script from github]
- run the script

That being said, (3) is the reason why (2) is significantly harder to do on v2.

An autoproj install has two bundler environments. One is dedicated to
autoproj and autoproj only. It's the one in .autoproj and is
completely isolated from the workspace's bundler environment.

The workspace environment "imports" the autoproj environment to get
the same version constraints w.r.t. autoproj and its dependencies.

The overall goal being that everything that is related to the "build"
is found in install/ and can be deleted at any time.

Sylvain

On Wed, May 31, 2017 at 2:38 PM, Thomas Roehr <thomas.roehr at dfki.de> wrote:
>> Nice. I'll add the v1-to-v2 transition info into the README and
>> generally speaking update the README.
> Yap, pasting the content of your former email (just rereading, see
> below) should already do
>
>>
>>> Open questions for me:
>>>
>>> 1. in order to install (manually) a gem into a workspace -- add the gem
>>> to .autoproj/Gemfile or .autoproj/Gemfile.lock and then bundle install?
>>
>> No ! Add to (not dot) autoproj/Gemfile and re-run `autoproj osdeps`. I
>> thought I mentioned that in my "autoproj v2" emails. Do NOT touch
>> .autoproj/Gemfile.
>
> My first search was unsuccessful, that's why I asked. But Gemfile seem
> to be a good keyword so could retrieve the mail again, thx.
>
>>
>>> 2. is there a good way of manually installing autoproj -- without using
>>> the bootstrap script, e.g., something comparably to (with autoproj v1)
>>
>> Well, there's no supported way to do it without running the
>> autoproj_install script (which only installs the autoproj environment
>> without doing a bootstrap). And the right question is: why there
>> should be ?
>
> Because I find it to be a robust, self sufficient and transparent
> process to start my installations.
> All tools are (most often) onboard and no need to look for an
> (potentially outdated) autoproj_install script.
>
>>
>>> 3. what is the redirection good for?
>>>         BUNDLE_GEMFILE=<dev>/install/gems/Gemfile
>>>         install/gems/Gemfile.lock --> .autoproj/Gemfile.lock
>>>         install/gems/Gemfile.lock --> .autoproj/Gemfile.lock
>>
>> What do you mean by "redirection" ?
> I assumed eval_gemfile '.autoproj/Gemfile' etc. to be some kind of
> redirection and would have expected: BUNDLE_GEMFILE=.autoproj/Gemfile.lock
>
> But since 'eval_gemfile' is Bundler DSL and with your hint to
> autoproj/Gemfile, I guess that this rather collects and injects all gem
> dependencies for bundler?
>
>
> --
> Thomas Röhr (M.Sc.)
> Space Robotics
>
> Besuchsadresse der Nebengeschäftstelle:
>  DFKI GmbH
>  Robotics Innovation Center
>  Robert-Hooke-Straße 5
>  28359 Bremen, Germany
>
>  Postadresse der Hauptgeschäftsstelle Standort Bremen:
>  DFKI GmbH
>  Robotics Innovation Center
>  Robert-Hooke-Straße 1
>  28359 Bremen, Germany
>
>  Tel.:     +49 421 178 45-4151
>  Zentrale: +49 421 178 45-0
>  Fax:      +49 421 178 45-4150 (Faxe bitte namentlich kennzeichnen)
>  E-Mail:   thomas.roehr at dfki.de
>
>  Weitere Informationen: http://www.dfki.de/robotik
>  -----------------------------------------------------------------------
>  Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
>  Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern
>  Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster
>  (Vorsitzender) Dr. Walter Olthoff
>  Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
>  Amtsgericht Kaiserslautern, HRB 2313
>  Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
>  USt-Id.Nr.:    DE 148646973
>  Steuernummer:  19/673/0060/3
>  -----------------------------------------------------------------------