Bug 55930 - Should mmp/mtouch/tools be added to $PATH
Summary: Should mmp/mtouch/tools be added to $PATH
Alias: None
Product: iOS
Classification: Xamarin
Component: Tools ()
Version: XI 10.10 (d15-2)
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2017-05-03 19:12 UTC by Chris Hamons
Modified: 2017-05-03 20:03 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Comment 1 Sebastien Pouliot 2017-05-03 19:31:21 UTC
I don't think it's worth it, at least for most* people.

Unlike Mono, XI and XM don't provide a lot of different tools tools and people generally use them thru an IDE (not the command-line).

* However it is rather useful for some people, including us and contributor. What I use personally is:

> alias mtouch="/Library/Frameworks/Xamarin.iOS.framework/Versions/Current/bin/mtouch"

in my `~/.bashrc`, so I don't have to care about the path.
Comment 2 Alexis Christoforides 2017-05-03 19:36:15 UTC
I am not sure whether or not this is useful for XI/XM, but this is the method for Mono.Framework (it doesn't directly add bin to the path):

In the bundle:

- create a new directory, "Commands"
- symlink specific binaries from /bin using a whitelist

At post-install time:

- create a new file under /etc/paths.d (called "mono-commands" but you would use any different name)
- write a single line in that file containing the full path to the "Commands" directory
Comment 3 Vincent Dondain [MSFT] 2017-05-03 20:03:45 UTC
Ok so I think the information to extract here is:

Are the tools we ship internal or external?

Indeed as Sebastien said the tools in XI/XM are generally used from the IDE (and that's good).

For e4k (and maybe tom swifty depending on how we ship it) or basically any tool that is not internal but for people to use we should update $PATH.

Let us close this bug as, I agree, for now there's no need to change XI/XM.