search

xiph / ogg

Reference implementation of the Ogg media container
BSD 3-Clause "New" or "Revised" License
345 stars 168 forks source link

Nuget #24

Open ghost opened 7 years ago

erikd commented 7 years ago

NuGet is a package manager for Windows? Is so, why does all this NuGet specific configuration need to be part of the Ogg repo? There is no Debian or Ubuntu or Fedora or OpenSuse or MacPorts specific stuff in this repo.

rillian commented 7 years ago

There's no deb or rpm packaging info because the distro packagers prefer to have their own packaging repos and having our own version make merges more work IIRC. We used to have them.

erikd commented 7 years ago

The point I was tyring to make is that nearly all other package managers and distros keep their distro specific packaging metadata in their own repos where is under their own control.

For instance, the libsndfile package metadata for libsndfile in OpenELEC is at https://github.com/OpenELEC/OpenELEC.tv/tree/master/packages/audio/libsndfile .

erikd commented 7 years ago

I still don't think this belongs in the Ogg git repo.

willson-chen commented 5 years ago

NuGet is a package manager for Windows? Is so, why does all this NuGet specific configuration need to be part of the Ogg repo? There is no Debian or Ubuntu or Fedora or OpenSuse or MacPorts specific stuff in this repo.

Agreed

ghost commented 5 years ago

Greetings, Thanks for the feedback. It was my understanding that the Contrib folder is for community contributions. that is where other projects have accepted nuget contributions. Any thoughts about the benefit of denying these contributions? I am confused and do not fully understand your reasoning. Thank you, Coast

On Sep 12, 2019, at 4:05 AM, willson-chen notifications@github.com wrote:

NuGet is a package manager for Windows? Is so, why does all this NuGet specific configuration need to be part of the Ogg repo? There is no Debian or Ubuntu or Fedora or OpenSuse or MacPorts specific stuff in this repo.

Agreed

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.