Bug 45854 - Links to nuget/mono not created
Summary: Links to nuget/mono not created
Alias: None
Product: Installers
Classification: Mono
Component: General ()
Version: 4.6.0 (C8)
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Rodrigo Kumpera
Depends on:
Reported: 2016-10-24 20:48 UTC by Dario
Modified: 2017-05-16 15:57 UTC (History)
3 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 GitHub or Developer Community 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:

Description Dario 2016-10-24 20:48:36 UTC
Description of Problem:
Fresh install of Xamarin Studio on a fresh install of macOS Sierra fails to install systemwide links to mono/nuget. Previous installations installed links to them so that they could be invoked via the command line and on CI systems.

Steps to reproduce the problem:
1. Install Xamarin Studio
2. Open Terminal
3. Run nuget

Actual Results:
Receive command not fond error

Expected Results:
nuget to be found and run

How often does this happen? 
every time

Additional Information:
Comment 1 Jeffrey Stedfast 2016-10-25 18:24:05 UTC
Xamarin Studio never set those symlinks, that was the job of the Mono installer.

I have no idea if anything changed there or what the reasons might have been, so reassigning to that team.
Comment 2 Dario 2016-10-25 22:05:43 UTC
OK, our CI build system, which run on clean OS X and Xamarin Studio installs, calls nuget by name (i.e. not by full path), and that has always worked. Recently did a fresh install of OS X and XS and nuget is not found on the path.
Comment 3 Rodrigo Kumpera 2016-10-31 22:30:55 UTC
Hey Alexis,

Could this be an installer issue?
Comment 4 Alexander Köplinger [MSFT] 2017-05-16 15:57:48 UTC
This is an intended change, see http://www.mono-project.com/docs/about-mono/releases/4.4.1/#changes-in-the-osx-installation-package

We no longer install anything into /usr/local/bin, but instead use /etc/paths.d/mono-commands for adding the "/Library/Frameworks/Mono.framework/Versions/Current/Commands" path to PATH (which should get run automatically by your shell).

Depending on how you start your shell/script this might not get executed, in those cases you can either run the eval() script mentioned in the link I posted above or modify PATH manually.