Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add developer documentation about environment setup #51

Merged
merged 4 commits into from
Nov 6, 2019

Conversation

dirk-thomas
Copy link
Member

Based on questions in colcon/colcon-core#262.

@dirk-thomas dirk-thomas added the review Waiting for review (Kanban column) label Nov 4, 2019
@dirk-thomas dirk-thomas self-assigned this Nov 4, 2019
@dirk-thomas dirk-thomas force-pushed the dirk-thomas/environment-setup branch from 18eddb6 to 687dd40 Compare November 4, 2019 22:49
@dirk-thomas dirk-thomas force-pushed the dirk-thomas/environment-setup branch from 687dd40 to 7af88c6 Compare November 4, 2019 22:53
Copy link
Contributor

@maryaB-osr maryaB-osr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a handful of little things

@dirk-thomas
Copy link
Member Author

@maryaB-osr Thanks for the improvements! I just removed two extra spaces in 4753935.

@dirk-thomas dirk-thomas merged commit 1c1c386 into master Nov 6, 2019
@delete-merged-branch delete-merged-branch bot deleted the dirk-thomas/environment-setup branch November 6, 2019 02:39

Therefore both parts are implemented in a Python script located in the root of the install prefix: ``_local_setup_util_<ext>.py``.
While the Python script itself can't change the environment it is able to efficiently interpret the operations described by the ``.dsv`` files and generate the shell specific commands necessary to update the environment.
The Python file is templated with information specific to the primary shell it used from hence the ``<ext>`` in the filename.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rationale for templating out multiple instances of the script rather than just passing arguments to one?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The templated approach was just easier to implement. The script logic only needs to take one set of formatting strings into account.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
review Waiting for review (Kanban column)
Development

Successfully merging this pull request may close these issues.

3 participants