Bug 240637 - [NEW PORT] devel/ros-rosinstall: a tool for keeping ROS workspaces in sync
Summary: [NEW PORT] devel/ros-rosinstall: a tool for keeping ROS workspaces in sync
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Kurt Jaeger
URL:
Keywords:
Depends on: 235843 235845 240638 240639
Blocks:
  Show dependency treegraph
 
Reported: 2019-09-17 10:52 UTC by Trenton Schulz
Modified: 2019-09-22 10:51 UTC (History)
2 users (show)

See Also:


Attachments
sharfile for devel/ros-rosinstall (2.79 KB, text/plain)
2019-09-17 10:52 UTC, Trenton Schulz
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Trenton Schulz 2019-09-17 10:52:49 UTC
Created attachment 207568 [details]
sharfile for devel/ros-rosinstall

Port for Rosinstall, a SCM abstracton tool for holding ROS workspaces in sync.
Comment 1 Kurt Jaeger freebsd_committer 2019-09-22 10:50:50 UTC
Committed, thanks!
Comment 2 commit-hook freebsd_committer 2019-09-22 10:51:14 UTC
A commit references this bug:

Author: pi
Date: Sun Sep 22 10:50:44 UTC 2019
New revision: 512579
URL: https://svnweb.freebsd.org/changeset/ports/512579

Log:
  New port: devel/ros-rosinstall

  Rosinstall is an SCM abstracton tool for holding ROS workspaces in sync.

  From the rosinstall documentation:

  Using rosinstall you can update several folders using a variety of
  SCMs (SVN, Mercurial, git, Bazaar) with just one command.

  That way you can more effectively manage source code workspaces.

  The rosinstall package provides a Python API for interacting with a
  source code workspace as well as a group of command line
  tools. Rosinstall leverages the vcstools package for source control
  and stores its state in .rosinstall files.

  rosinstall was developed to help with the ROS software, but it has no
  install dependencies to ROS. It offers support for ROS environments
  and thus makes some assumptions about ROS being present at runtime,
  but those can be easily removed and rosws provides all services even
  when there is no ROS installed. The vision is for the bulk of
  rosinstall to be a ROS agnostic tool one day.

  WWW: http://docs.ros.org/independent/api/rosinstall/html

  PR:		240637
  Submitted by:	Trenton Schulz <trueos@norwegianrockcat.com>

Changes:
  head/devel/Makefile
  head/devel/ros-rosinstall/
  head/devel/ros-rosinstall/Makefile
  head/devel/ros-rosinstall/distinfo
  head/devel/ros-rosinstall/pkg-descr