Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Assigning packages to license types
-
The ability to assign a package to a license type only appears for a subset of packages, it seems only those which contain a licenseURL in the nuspec (using NuGet as an example) allow the association to be made. Some packages could still be attributed accurately to a license type as people have been know to put refer to the license in the description for example.
Is there any way to make that association if the UI does not make it available?
Are there any plans to update the UI to allow it in the future?There is no way in the UI to visualize that a package is blocked from download because you have applied controls to the allowed license types with out going into each package. Has any thought been given to visualizing that on the feed summary page?
Product: ProGet
Version: 5.0.12 -
This is by design; it is the responsibility of a package author to license a package, and make sure that it's a standard license. This way, automated licensing monitoring can catch it. However, as you've noticed, this isn't the case for a lot of open source packages.
So, in this case, you'll want to use a different workflow. Just create a "approved packages" feed, and promote approved packages into these feeds.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login