Ok, I appreciate it, and sorry to be a bother, but could you fork this repo (<a href="https://github.com/adamv/homebrew-alt">https://github.com/adamv/homebrew-alt</a>) instead of making a new one? It has to be forked via github for it to be discovered.<div>
<br></div><div>Thanks for your help,</div><div><br clear="all">~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>William Woodall<br>Graduate Software Engineering<br>Auburn University<br><a href="mailto:w@auburn.edu" target="_blank">w@auburn.edu</a><br>
<a href="mailto:wjwwood@gmail.com" target="_blank">wjwwood@gmail.com</a><div><a href="http://williamjwoodall.com" target="_blank">williamjwoodall.com</a><br>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</div><br>
<br><br><div class="gmail_quote">On Wed, Oct 19, 2011 at 3:20 PM, Troy Straszheim <span dir="ltr"><<a href="mailto:straszheim@willowgarage.com">straszheim@willowgarage.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<a href="https://github.com/ros/homebrew" target="_blank">https://github.com/ros/homebrew</a><br>
<br>
have at it...<br>
<div><div></div><div class="h5"><br>
On Wed, Oct 19, 2011 at 1:13 PM, William Woodall <<a href="mailto:wjwwood@gmail.com">wjwwood@gmail.com</a>> wrote:<br>
> It doesn't necessarily, but these would be ROS specific formulae that would<br>
> exist outside of the Homebrew proper repo. We are experimenting with using<br>
> "brew taps" which are discovered automatically via the github fork network.<br>
> So if we fork homebrew-alt to the ros organization and call it ros-deps,<br>
> then we can do something like `brew tap install ros/ros-deps` and then we<br>
> can install custom formulae like tinyxml and others without having to put<br>
> them upstream into the Homebrew repository via a pull request. It would<br>
> also potentially have ros stacks that could be distributed as binaries in<br>
> the future.<br>
> Basically the '<a href="http://github.com/ros" target="_blank">github.com/ros</a>' name is convenient.<br>
> Thanks,<br>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
> William Woodall<br>
> Graduate Software Engineering<br>
> Auburn University<br>
> <a href="mailto:w@auburn.edu">w@auburn.edu</a><br>
> <a href="mailto:wjwwood@gmail.com">wjwwood@gmail.com</a><br>
> <a href="http://williamjwoodall.com" target="_blank">williamjwoodall.com</a><br>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
><br>
><br>
> On Wed, Oct 19, 2011 at 3:07 PM, Troy Straszheim<br>
> <<a href="mailto:straszheim@willowgarage.com">straszheim@willowgarage.com</a>> wrote:<br>
>><br>
>> On Wed, Oct 19, 2011 at 12:54 PM, Troy Straszheim<br>
>> <<a href="mailto:straszheim@willowgarage.com">straszheim@willowgarage.com</a>> wrote:<br>
>> > That'd be me.<br>
>> ><br>
>><br>
>> Hmm. Why does homebrew belong under ros?<br>
>><br>
>><br>
>> > On Wed, Oct 19, 2011 at 12:26 PM, William Woodall <<a href="mailto:wjwwood@gmail.com">wjwwood@gmail.com</a>><br>
>> > wrote:<br>
>> >> Does anyone know who has control over the ros organization on github?<br>
>> >> <a href="https://github.com/ros" target="_blank">https://github.com/ros</a><br>
>> >> We would like access to it in order to create a repository for Homebrew<br>
>> >> on<br>
>> >> OS X if anyone knows about it.<br>
>> >> Thanks,<br>
>> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
>> >> William Woodall<br>
>> >> Graduate Software Engineering<br>
>> >> Auburn University<br>
>> >> <a href="mailto:w@auburn.edu">w@auburn.edu</a><br>
>> >> <a href="mailto:wjwwood@gmail.com">wjwwood@gmail.com</a><br>
>> >> <a href="http://williamjwoodall.com" target="_blank">williamjwoodall.com</a><br>
>> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
>> >><br>
>> >> _______________________________________________<br>
>> >> ros-users mailing list<br>
>> >> <a href="mailto:ros-users@code.ros.org">ros-users@code.ros.org</a><br>
>> >> <a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/listinfo/ros-users</a><br>
>> >><br>
>> >><br>
>> ><br>
>> _______________________________________________<br>
>> ros-users mailing list<br>
>> <a href="mailto:ros-users@code.ros.org">ros-users@code.ros.org</a><br>
>> <a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/listinfo/ros-users</a><br>
><br>
><br>
> _______________________________________________<br>
> ros-users mailing list<br>
> <a href="mailto:ros-users@code.ros.org">ros-users@code.ros.org</a><br>
> <a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/listinfo/ros-users</a><br>
><br>
><br>
_______________________________________________<br>
ros-users mailing list<br>
<a href="mailto:ros-users@code.ros.org">ros-users@code.ros.org</a><br>
<a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/listinfo/ros-users</a><br>
</div></div></blockquote></div><br></div>