Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release vorbis as vs2017 NuGet package #30

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Release vorbis as vs2017 NuGet package #30

wants to merge 1 commit into from

Conversation

ghost
Copy link

@ghost ghost commented Oct 3, 2017

No description provided.

@erikd
Copy link
Member

erikd commented Oct 3, 2017

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

@ghost
Copy link
Author

ghost commented Oct 3, 2017

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
Copy link
Member

erikd commented Oct 3, 2017

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
Copy link
Author

ghost commented Oct 3, 2017

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
Copy link
Member

erikd commented Oct 4, 2017

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
Copy link
Author

ghost commented Oct 4, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant