Is your feature request related to a problem? Please describe.
I would like to use the export --nuget command to package multiple libraries into one NuGet-package. This package will be available to other developers at my company via an company-internal NuGet-feed. To communicate information about the contents of the package with others, I would like to use the description of the package. Currently the default description of an exported NuGet-package is just "Vcpkg NuGet export" and i have not found an argument for the export command to change it.
Proposed solution
I would propose the addition of a --nuget-description argument for the export command. Therefore the option_implies call for the OPTION_NUGET and the opts.nuget conditional branch in handle_raw_based_export(...) in the export.cpp need to be modified (if understand the source correctly).
Describe alternatives you've considered
As an alternative, I considered concatenating the names and the targets of the included libraries in the name of the exported NuGet-package with the --nuget-id argument. But in my humble opinion, that approach does not scale very well and defeats the purpose of packaging multiple libraries together in a package with a strong and concise name.
Is your feature request related to a problem? Please describe.
I would like to use the
export --nugetcommand to package multiple libraries into one NuGet-package. This package will be available to other developers at my company via an company-internal NuGet-feed. To communicate information about the contents of the package with others, I would like to use the description of the package. Currently the default description of an exported NuGet-package is just "Vcpkg NuGet export" and i have not found an argument for theexportcommand to change it.Proposed solution
I would propose the addition of a
--nuget-descriptionargument for theexportcommand. Therefore theoption_impliescall for theOPTION_NUGETand theopts.nugetconditional branch inhandle_raw_based_export(...)in the export.cpp need to be modified (if understand the source correctly).Describe alternatives you've considered
As an alternative, I considered concatenating the names and the targets of the included libraries in the name of the exported NuGet-package with the
--nuget-idargument. But in my humble opinion, that approach does not scale very well and defeats the purpose of packaging multiple libraries together in a package with a strong and concise name.