DotNet package manager

Edit Package nuget

This build uses a drop-in replacement for Microsoft.Web.XmlTransform, derived from XDT (which is under Apache 2 License) in order to solve license issues with the original.

Refresh
Refresh
Source Files
Filename Size Changed
_service 0000000473 473 Bytes
nuget-2.8.3.tar.bz2 0014049548 13.4 MB
nuget.changes 0000000619 619 Bytes
nuget.sh 0000000117 117 Bytes
nuget.spec 0000003570 3.49 KB
packages.tgz 0006574698 6.27 MB
xdt.tar.gz 0000047495 46.4 KB
Latest Revision
Stephen Shaw's avatar Stephen Shaw (decriptor) accepted request 266908 from Matthias Mailänder's avatar Matthias Mailänder (Mailaender) (revision 3)
also fixed Error: SendFailure (Error writing headers) by automatizing the certificate import in %post
Comments 3

Star Brilliant's avatar

The latest nuget is 3.5.0. Can we upgrade it?


Hammer Faceman's avatar

Nuget 3.5 is not fully compatible with mono according to it's release notes. Also, it seems impossible to build current nuget with mono right now (see https://github.com/NuGet/NuGet.Client).

As far as I know, you can use your own precompiled nuget-binary (downloaded from https://dist.nuget.org) when building your projects with xbuild from command-line, it should work fine.

If you are using Monodevelop from Mono:Factory - it is also a deprecated package. And it is not possible to update nuget binary that is used internally by Monodevelop - it is relying on it's own exact version. So, if you need a newer nuget version for use with Monodevelop - you must deploy a newer Monodevelop instead: it using flatpak distribution now. (it is also hard to build newer Monodevelop with OBS due to major changes in build process, so it also may be never updated)


Jon Brightwell's avatar

They're up to version 5.7. Looks like their build.sh pulls in dotnet cli, but maybe that can be worked with. Is it worth another look at this? They don't make it easy to do packaging, that's for sure.

openSUSE Build Service is sponsored by