Anyone want to maintain a chocolatey package? |
MrOzBarry
|
Hey Guys and Gals,
Has anyone heard of chocolatey, a package manager for Windows? Â Just discovered it a few days ago, and see there aren't any SDL packages. Â Any thoughts? Â I don't mind maintaining it myself, but I don't want to start something that someone else has already taken up. Â Any merits or downsides anyone can think of? -Alex |
|||||||||||
|
Anyone want to maintain a chocolatey package? |
Scott Percival
Guest
|
Would there be a need for it? Chocolatey is more geared for deploying applications, it doesn't at all map to the Linux package manager standard of e.g. having every shared library as a seperate package with a dependency list. Typically if a Windows application requires SDL, it bundles a DLL; there isn't an expectation that it should be preinstalled on the system.
On 23 July 2014 09:10, Alex Barry wrote:
|
|||||||||||||
|
Anyone want to maintain a chocolatey package? |
MrOzBarry
|
Well, it would be more-so for developers than end-users, but it could work for both if developers deploy their applications on chocolatey as well. Â That's not to say that I disagree with you that best-case scenario is bundling with your own build of SDL upon deployment.
-Alex On Tue, Jul 22, 2014 at 11:19 PM, Scott Percival wrote:
|
|||||||||||||||
|
Anyone want to maintain a chocolatey package? |
Scott Percival
Guest
|
Ahh, as in NuGet, to let Visual Studio people get the latest build? That would make a bit more sense... e.g. there's an old 1.2 package available http://www.nuget.org/packages/SDL/ . (don't know much about NuGet save that Chocolately was built off it, I'm guessing hardcore VS users will like it?)
On 23 July 2014 11:29, Alex Barry wrote:
|
|||||||||||||||||
|