[vlc-devel] libvlc on NuGet

[Jeremy Vignelles]

I just saw that my previous mail was sent in text/html rather than plain/text. Apologies.

Below is a version of the previous mail:

> Hi,
> 
> I am contributing to an open source VLC wrapper for .net (ZeBobo5/Vlc.DotNet).
> 
> The current process of using the library for a .net project is:
> 
> - Install Vlc.DotNet through the NuGet package manager.
> 
> - Download manually and install Vlc libraries from the official website.
> 
> - Configure the project to set the correct path of the Vlc library, depending on where you installed it.
> 
> I would like to simplify that process by adding the native libvlc files to NuGet, so that they can be installed and the project configured as needed.
> 
> I could package it by myself, push it to NuGet and create Yet Another LibVlc Distribution, but I like standard things, especially for production. That's why I think that would be better to have a "VideoLan" package, built each time a VLC is out and that is pushed to NuGet. I can help for that.
> 
> What would involved:
> 
> - Setup a build environment (could be a linux docker image I suppose, based on microsoft/dotnet image)
> 
> - Write the .nuspec file that contains the package metadata
> 
> - Create a "videolan" account on NuGet
> 
> - Wire things up so that:
> 
>    - The vlc release is downloaded
> 
>    - The release is extracted and files are copied next to the .nuspecfiles
> 
>    - `dotnet pack` is called with the package version as an argument (prereleases can be published with a x.y.z-beta1)
> 
>    - The package is published to NuGet
> 
> Repeat for each package, at least :
> 
> - Windows x86
> 
> - Windows x64
> 
> And optionally, since .net core is opening the way to .net on everything, include the other platforms too.
> 
> What do you think about it?

Thanks,
cube45