Posts: 12,706
Joined: Nov 2003
Reputation:
129
spiff
Team-Kodi Member
Posts: 12,706
wow! windows has finally discovered the wonders of the 90s!
Posts: 5,184
Joined: Jan 2009
Reputation:
131
I've used NuGet a few times in .NET applications but only really from the "user" side (I only once published a NuGet package in our companies NuGet repository) and I have to admit it's pretty sweet.
The main problem I see in combination with XBMC is that we usually use a very specific version of a library and in most cases not the most recent one (for good reasons). I'm not sure how that is possible/handled by NuGet. Furthermore we couldn't push libraries that we need to NuGet because we don't want to (and can't) maintain them so it would be up to the maintainers of those libraries to do that.
In the end that would probably leave us with two ways to get/handle dependencies on win32 which might become confusing and would also require to maintain both of them. I'm not saying I don't like the idea but it only really makes sense if there already are a lot of libraries used by XBMC available as NuGet packages (in the necessary version).
Always read the
online manual (wiki),
FAQ (wiki) and search the forum before posting.
Do not e-mail Team Kodi members directly asking for support. Read/follow the
forum rules (wiki).
Please read the pages on
troubleshooting (wiki) and
bug reporting (wiki) before reporting issues.
Posts: 252
Joined: May 2009
Reputation:
10
Paxxi
Team-Kodi Member
Posts: 252
Versioning shouldn't be a big problem, as long as it's provided you can install an older version or afaik, pin it to that version.
yeah Spiff, I think someone felt envy when ruby gems was the hot thing and wanted to have that, admittedly they've done a good job for the .net and javascript side of it.
I'll try and look at how much work it would be to maintain packages and try to get working on it to test it out, hopefully will have some time over the weekend
Posts: 5,184
Joined: Jan 2009
Reputation:
131
2013-09-12, 11:19
(This post was last modified: 2013-09-12, 11:20 by Montellese.)
@Trem: The problem with older versions might be that they won't ever make it into a NuGet repository because they may already be very old.
EDIT: Obviously XBMC could setup its own NuGet repository and upload all its dependencies there. That would save the extra work to write scripts for the dependency download etc.
Always read the
online manual (wiki),
FAQ (wiki) and search the forum before posting.
Do not e-mail Team Kodi members directly asking for support. Read/follow the
forum rules (wiki).
Please read the pages on
troubleshooting (wiki) and
bug reporting (wiki) before reporting issues.
Posts: 11,582
Joined: Feb 2008
Reputation:
84
davilla
Retired-Team-XBMC Developer
Posts: 11,582
just setup our own NuGet repository and use that, we have the servers and we already squirrel away any tarballs we need to build in the mirrors.
Posts: 2,745
Joined: Oct 2003
Reputation:
1
WiSo
Team-Kodi Developer
Posts: 2,745
Quite some time ago I looked for a package manager on windows since I wanted to get rid of our custom scripts. Unfortunately nothing was very major. I don't know NuGet but if its works and doesn't make more effort than our current solution why not. But an own repo is a must.