Skip to content

Patches from Steven on https://code.ros.org/trac/ros/ticket/3915#1

Merged
tfoote merged 2 commits intoros-infrastructure:masterfrom
tfoote:master
Apr 5, 2012
Merged

Patches from Steven on https://code.ros.org/trac/ros/ticket/3915#1
tfoote merged 2 commits intoros-infrastructure:masterfrom
tfoote:master

Conversation

@tfoote
Copy link
Copy Markdown
Member

@tfoote tfoote commented Apr 5, 2012

Practicing pull request workflow.

tfoote added a commit that referenced this pull request Apr 5, 2012
@tfoote tfoote merged commit e638af5 into ros-infrastructure:master Apr 5, 2012
ktossell added a commit to ktossell/rosdep that referenced this pull request Oct 2, 2013
I've added 'aur' as a separate installer type, to be used as follows:

dep_name:
  arch:
    aur: [my_aur_pkg]

When rosdep is initialized, it searches for yaourt and packer in your
path, and if either one is found, rosdep will register the AUR installer
with the discovered script (using packer if both are found).

I considered the following alternative arrangements:

dep_name:
  arch: [aur/aur_pkg, official_pkg, community/aur_pkg2]
  # Here, 'aur/'-prefixed packages go to packer, otherwise pacman.

dep_name:
  arch:
    packer: [aur_pkg]

The major advantage of alternative ros-infrastructure#1 is that it allows you to
specify both AUR and official packages to satisfy a single dependency
key. Per REP 111, "rosdep rules are only allowed to specify a single
package manager to fulfill them." So far this only affects the 'eclipse'
rule, which required the 'eclipse' package and three AUR packages.
ktossell added a commit to ktossell/rosdep that referenced this pull request Feb 20, 2014
I've added 'aur' as a separate installer type, to be used as follows:

dep_name:
  arch:
    aur: [my_aur_pkg]

When rosdep is initialized, it searches for yaourt and packer in your
path, and if either one is found, rosdep will register the AUR installer
with the discovered script (using packer if both are found).

I considered the following alternative arrangements:

dep_name:
  arch: [aur/aur_pkg, official_pkg, community/aur_pkg2]
  # Here, 'aur/'-prefixed packages go to packer, otherwise pacman.

dep_name:
  arch:
    packer: [aur_pkg]

The major advantage of alternative ros-infrastructure#1 is that it allows you to
specify both AUR and official packages to satisfy a single dependency
key. Per REP 111, "rosdep rules are only allowed to specify a single
package manager to fulfill them." So far this only affects the 'eclipse'
rule, which required the 'eclipse' package and three AUR packages.
wjwwood pushed a commit that referenced this pull request Apr 11, 2014
…atch

use custom mechanism for --skip-keys
wjwwood pushed a commit that referenced this pull request Apr 11, 2014
wjwwood pushed a commit that referenced this pull request Mar 2, 2015
Small tweaks of the new `--filter-for-installers` argument.
wjwwood pushed a commit that referenced this pull request Mar 14, 2018
* Mac support (#1)

* Run CI on both linux and osx

* Introduce matrix for OSes with generic language for osx

* Matrix include does not recognize list of python versions.  Create an entry for every version

* Fix typo

* Remove empty line

* Install pyenv for osx

* Fix syntax error in the script

* Fix bash syntax error

* Remove set from the script

* Remove reference to the current directory while running install.sh

* Try v.env 2.7

* Print venv

* Install python with penv

* Fix typo in the scipt

* install mock

* Skip some tests on macOS

* Enable tests on linux to see the results

* Do not skip debian tests on mac - this is just wrong

* Fix test_dpkg_detect so it does not call apt-cache on Mac

* Fix test_AptInstalleso it does not call debian specific commands on Mac

* Fix test_rosdep_main.TestRosdepMain.test_install on Mac

* Print call_args_list for the first call in the test

* Change env. variable for python installation, make it consistent with TRAVIS

* Remove assert for the first command.  Order of parameters differs on various platforms.

* There is no version 3.4 in pyenv.  Use the latest in 3.4

* Match output with a run on Ubuntu

* Add EOL to the file

* Remove echo with python version env. variable

* Remove useless comment

* Switch Python for macOS to versions 2.7.14 and 3.6.4 to be consistent with the version installed by `brew python`

* Build and test on python installed from brew (#2)

Add a new job that uses python installed from brew.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant