[ros-users] bash specific functionality removed from setup.sh into setup.bash
Garratt
garrattgallagher at gmail.com
Tue Feb 8 04:23:37 UTC 2011
I'm actually most in favor of manually adding [ATTENTION DEVELOPERS]
to the subject line, and publishing it to ros-users.
This has several benefits:
-it includes anyone who is already getting emails, so no-one would have
to 'take action' if they were not affected (i.e. is they actually
inspect every email they get anyway)
-Personally, if an additional list came out, I would just end up adding
it to the one email account that gets all my ros mail already, and
applying a filter to flag those emails. Applying a filter to a new tag
just eliminates one of those steps.
-Not that I want to encourage shouting on the mailing list to get
attention, it does work. Tully, when you sent out the email this
afternoon about eigen3, it immediately caught my eye.
cheers
Garratt
On Mon, 2011-02-07 at 16:54 -0800, Tully Foote wrote:
> I've ticketed this so we don't lose track of it
> https://code.ros.org/trac/ros/ticket/3307
>
> On Thu, Jan 20, 2011 at 7:49 PM, Daniel Stonier <d.stonier at gmail.com>
> wrote:
>
>
> On 21 January 2011 10:40, Tully Foote
> <tfoote at willowgarage.com> wrote:
>
>
> On Thu, Jan 20, 2011 at 4:28 PM, garratt
> <garrattgallagher at gmail.com> wrote:
> Hi Tully,
>
> First off, Is there any chance that there
> could be some sort of
> additional mailing list/RSS feed for
> announcements like this that change
> functionality for most users? I subscribe to
> all the mailing lists, and
> really important messages like this one tend
> to get lost in the noise.
> Actually, even a [Announcement] tag after the
> normal [ros-users] might
> do...
>
>
> if we put this sort of thing into the ROS.org News
> Feed would that be a good solution?
> http://www.ros.org/news/
>
>
> Actually, could probably use its own feed. The ros.org news
> feed is closely followed by most of the people here at our
> company who are keen ros observers, but not ros developers.
> They love to see ros robots and who is using ros. Posting
> there would just mean important announcements to developers on
> actual ros functionality changes would get lost in a different
> kind of noise. Those of us who actually develop with ros here
> don't actually follow that feed much as we already know what's
> going on. It would also generate unnecessary noise for the ros
> observers.
>
>
>
> secondly, I'd like to point out that the
> output of rosinstall still
> says:
> "
> done. Now, type 'source /somepath/setup.sh' to
> set up your environment.
> Add that to the bottom of your ~/.bashrc to
> set it up every time.
> "
> If we are moving to support other shells,
> shouldn't this be changed? It
> would have certainly caught my eye if it was:
>
> Add 'source /somepath/setup.bash' to your
> ~/.bashrc if you are using
> bash shell
> add 'source /somepath/setup.zsh' to your
> ~/.tzrc if you are using zsh
> shell (or whatever the config file is
> named...)
>
> Or, given that you can find which shell is
> being used, just print the
> relevant setup suffix...
>
> Thanks, i missed that. Ticketed
> https://code.ros.org/trac/ros/ticket/3264
>
> Tully
>
>
> thanks,
> Garratt
>
>
>
>
> On Thu, 2011-01-13 at 15:35 -0800, Tully Foote
> wrote:
> > Hi,
> >
> > As of rosinstall version 0.5.12 it will no
> longer use bashisms in the
> > setup.sh file. They have been moved to
> setup.bash. And for zsh users
> > there is also a setup.zsh generated.
> >
> > For existing bash users this will mean that
> until you switch to use
> > setup.bash instead of setup.sh you will not
> have the command line tools
> > you are used to such as rosrun roscd and tab
> completion.
> >
> > This was ticketed at
> https://code.ros.org/trac/ros/ticket/2860
> >
> > I have tried to update references on the
> wiki. If you run into one I
> > missed please update it to reference
> setup.bash, unless the reference is
> > for a specific different shell.
> >
> > A similar change will be made in
> the /opt/ros/ROSDISTRO/setup.sh will be
> > seperated to setup.sh for environment and
> setup.bash for bash specific
> > calls. TIcketed at
> https://code.ros.org/trac/ros/ticket/3243
> >
> > Tully
> >
> >
>
> >
> _______________________________________________
> > ros-users mailing list
> > ros-users at code.ros.org
> >
> https://code.ros.org/mailman/listinfo/ros-users
>
>
> _______________________________________________
> ros-users mailing list
> ros-users at code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
>
>
> --
> Tully Foote
> Systems Engineer
> Willow Garage, Inc.
> tfoote at willowgarage.com
> (650) 475-2827
>
> _______________________________________________
> ros-users mailing list
> ros-users at code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
>
>
> _______________________________________________
> ros-users mailing list
> ros-users at code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
>
>
>
> --
> Tully Foote
> Systems Engineer
> Willow Garage, Inc.
> tfoote at willowgarage.com
> (650) 475-2827
> _______________________________________________
> ros-users mailing list
> ros-users at code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
More information about the ros-users
mailing list