<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Daniel,<br>
<br>
yes, current yaml ignores uri for elements of type "other".<br>
<br>
You can call "rosinstall . <a moz-do-not-send="true"
href="http://rnd.yujinrobot.com/ycs.rosinstall">http://rnd.yujinrobot.com/ycs.rosinstall</a>".
By calling this again you also get updates from <a
moz-do-not-send="true"
href="http://rnd.yujinrobot.com/ycs.rosinstall">http://rnd.yujinrobot.com/ycs.rosinstall</a>
(only adding new locations or changing urls/versions, but not
removing anything).<br>
<br>
If <a moz-do-not-send="true"
href="http://rnd.yujinrobot.com/ycs.rosinstall">ycs.rosinstall</a>
has elements with localnames such as <br>
<br>
- git: <br>
local-name: ycs/foo<br>
uri: <a moz-do-not-send="true"
href="https://win-ros-pkg.googlecode.com/svn/stacks/win_ros/trunk">https://somewhere.com/foo.git</a><br>
<br>
I think you can have most of what you want already.<br>
<br>
You can then maintain several such rosinstall files and keep merging
them into your environment (by calling rosinstall . <a
moz-do-not-send="true"
href="http://rnd.yujinrobot.com/ycs.rosinstall">http://rnd.yujinrobot.com/ycs.rosinstall</a>",
which can be in a script)<br>
<br>
That's maybe not exactly what you want, but close.<br>
<br>
Else, maybe describe your workflow also.<br>
<br>
cheers,<br>
Thibault<br>
<br>
<br>
On 10/21/2011 10:46 AM, Daniel Stonier wrote:
<blockquote
cite="mid:CAP6aRqYYooZgjDqTv90rA1QnK8ynNfJw9Lq5g2561dUkrWc46g@mail.gmail.com"
type="cite">
<div><br>
</div>
Hi all,
<div><br clear="all">
<div>Pretty sure this can't be done with the current yaml so I
guess it falls in the area of a feature request. </div>
<div><br>
</div>
<div>e.g. envisioning a rosinstall file that would look
something like:</div>
<div><br>
</div>
<div>
<div>- other: </div>
<div> local-name: /opt/ros/electric/ros</div>
<div><br>
</div>
<div>- other: </div>
<div> local-name: ycs</div>
<div> uri: <a moz-do-not-send="true"
href="http://rnd.yujinrobot.com/ycs.rosinstall">http://rnd.yujinrobot.com/ycs.rosinstall</a></div>
<div><br>
</div>
<div>- svn:</div>
<div> local-name: win_ros</div>
<div> uri: <a moz-do-not-send="true"
href="https://win-ros-pkg.googlecode.com/svn/stacks/win_ros/trunk">https://win-ros-pkg.googlecode.com/svn/stacks/win_ros/trunk</a></div>
<div>
<br>
</div>
<div>- git:</div>
<div> uri: <a moz-do-not-send="true"
href="https://github.com/stonier/qt_ros.git">https://github.com/stonier/qt_ros.git</a></div>
<div> local-name: qt_ros</div>
<div> version: master</div>
<div><br>
</div>
<div>where ycs.rosinstall conveniently collects and maintains
its own working set. This would be fairly convenient to our
workflow, would it be a useful addition for others in
general?</div>
</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Daniel Stonier.</div>
<div><br>
</div>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
ros-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ros-users@code.ros.org">ros-users@code.ros.org</a>
<a class="moz-txt-link-freetext" href="https://code.ros.org/mailman/listinfo/ros-users">https://code.ros.org/mailman/listinfo/ros-users</a>
</pre>
</blockquote>
<br>
</body>
</html>