Bug 33857 - nuget command is missing from /usr/bin on OSX 10.11 El Capitan
Summary: nuget command is missing from /usr/bin on OSX 10.11 El Capitan
Alias: None
Product: Installers
Classification: Mono
Component: General ()
Version: 4.2.0 (C6)
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Alexis Christoforides
Depends on:
Reported: 2015-09-10 16:11 UTC by Jon Dick
Modified: 2015-09-11 14:08 UTC (History)
1 user (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 Jon Dick 2015-09-10 16:11:26 UTC
Since /usr/bin is write restricted on OSX 10.11 El Capitan, /usr/bin/nuget is missing.  I've added a symlink for /usr/local/bin/nuget which solves the issue for me, would be nice to have this in the mono install :)
Comment 1 Rodrigo Kumpera 2015-09-11 09:26:43 UTC
I assume you mean adding a symlink to /usr/local/bin?

Alexis, 4.0 ships /usr/bin/nuget but apparently the El Capitan package doesn't have /usr/local/bin/nuget. Could you look into it?
Comment 2 Alexis Christoforides 2015-09-11 14:08:17 UTC
I hadn't commited the El Capitan change for the lane 4.2 lane, sorry. It's already in 4.0 and master. We probably missed it in QA because if the symlinks are installed from a previous package once, they'll still be there and working. The latest packages being built have the fix.