Any way to publish packages that are *always* unlisted?

Feb 3, 2012 at 1:48 PM

I have several packages that by themselves are useless -- they merely are present to act as dependencies of other packages so that I have a "package per assembly" to avoid packages overlapping each others' dll's.  However when folks look at the list of packages they're overwhelmed and can't choose which one they want.  The story would be much improved if all these intermediate packages were hidden -- only available as dependencies.

Is such a thing possible?

Feb 3, 2012 at 3:12 PM

I believe right now when you publish a package, by default it's listed. Then you need to go to nuget.org to unlist it. But I think it's a good feature to allow publishing a package and having it unlisted by default.

You can create a feature request for nuget.org gallery at: https://github.com/NuGet/NuGetGallery

Feb 3, 2012 at 3:37 PM
Edited Feb 3, 2012 at 3:39 PM

Where does that nuget gallery issues tracker fall compared to this CodePlex project's Issue Tracker?  Does one get paid attention to more?

Filed issue https://github.com/NuGet/NuGetGallery/issues/401

Feb 3, 2012 at 3:47 PM

Yup, it's a bit confusing. This codeplex project covers the NuGet Visual Studio extension plus the command line nuget.exe.

The Github project covers the nuget.org website (including the official feed and publishing services).