Allow gem maintainer to notify nu to not actually install a package in to the lib

[brendanjerwin]

Some packages are really just tooling for development. There should be a way to notify nu not to install in the lib after gem has done its thing. That way users wouldn't have to know the difference and could just go about their lives in blissful ignorance...

[kiliman]

I'm not sure I understand this one. If the gem is not a lib to be referenced, why would a developer use "nu install" instead of simply "gem install"?

And even if they did use "nu install", there's no harm. Maybe the developer wanted to check in the tools to version control.

[brendanjerwin]

Yes, a user could (currently) just use gem install, but what about in the future once we have our own gem server up and running and have modified nu gems past the point that they are compatible with ruby gems?

Also, if the developer were to install the binaries into their lib, would Nu set PATH to include their project's Lib? That doesn't seem right, but if it didn't the developer couldn't launch the tool without specifying the entire path to it.

[ferventcoder]

gem install ftw.