Release vorbis as vs2017 NuGet package

[ghost]

No description provided.

[erikd]

Why is this being contributed here? Doesn't this belong in some NuGet repository?

[ghost]

Greetings erikd,

The NuGet repository is own by Microsft, think of it as the generic apt or yum of windows.
The packaging scripts usually are contained within the source trees.
I can alter the scripts to get you traffic via linking to this repo if that is helpful.

Thanks,
coast

[erikd]

The Vorbis repo does not contain packaging metadata for any of the (over 100) Linux distributions. So why should it contain packaging metadata for NuGet?

[ghost]

The vorbis repo benefits from nuget distribution because of one main reason, vorbis was completely unusable with visual studio 2013-2017. The msvc project files included in the repo are not sufficient. now people can install vorbis for their visual studio project with ease. I view the nuget as the modernization of the deprecated msvc project files. Install-Package vorbis-msvc no need to compile anything, the library is hosted on the cloud. the source tree should own the compilation method. nuget servers own the distribution. What are your thoughts?

[erikd]

the source tree should own the compilation method.

I disagree. There are over 100 Linux distrinutions with at least 5 different packaging formats, Mac OS has Brew and a number of others and there is at least one other package management system on Windows. None of these systems have their package metadata in the Vorbis repo. Therefore I can't see why NuGet is different.

In addition, I suspect that most Open Source projects that started on Linux will take the same attitude.

As an example, I am the main maintainer of libsndfile and FLAC. They have NuGet entries here:

https://www.nuget.org/packages/libsndfile-msvc14-x64/
https://www.nuget.org/packages/FLAC.WindowsRuntime/

and yet neither of those projects have NuGet metadata in their source trees.

[ghost]

Greetings, It seems you are dissuaded and that is your prerogative. Know that I maintain these nugets (including libsndfile linked above) for the end users to enjoy. You can take this gift from me, or you can close the pull requests. Doesn’t matter to me because the package usage statistics speak for themselves. Also know that the libraries you maintain are being the first rejection of user contributions that I have experienced in this manner. Again this is your prerogative. As a counter example to your points above, GPL GSL gladly accepted my nuget scripts. So the trend is mixed among Linux libraries. Thanks, Coast

…

On Oct 4, 2017, at 2:37 AM, Erik de Castro Lopo ***@***.***> wrote: the source tree should own the compilation method. I disagree. There are over 100 Linux distrinutions with at least 5 different packaging formats, Mac OS has Brew and a number of others and there is at least one other package management system on Windows. None of these systems have their package metadata in the Vorbis repo. Therefore I can't see why NuGet is different. In addition, I suspect that most Open Source projects that started on Linux will take the same attitude. As an example, I am the main maintainer of libsndfile and FLAC. They have NuGet entries here: https://www.nuget.org/packages/libsndfile-msvc14-x64/ https://www.nuget.org/packages/FLAC.WindowsRuntime/ and yet neither of those projects have NuGet metadata in their source trees. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.