The new stable version is out...
given nothing in the tree uses it, was it agreed to have dotnet herd in metadata ? What was the reason for adding it in the first place ?
Now I must stand in for whoever has added it to the tree. It may be not depended on by any package, still our company uses this cool lib extensively so this has solved a lot of overlay messing for us. Thanks and please don't remove the package, our company is and will be using it so at least we'll ensure it works.
That is not really the point, sure anything is used by someone somewhere, that doesn't necessarily mean it should be in the tree. For local usage it is peanuts to create an overlay with your own ebuild, that is one of the strong points of gentoo's ebuild system. This stable release is almost a month old, so it seems to me the maintainership in Gentoo is not up to par.
Umm, my english is not that good. What does "up to par" mean, please?
Created attachment 85343 [details] nini-1.1.0.ebuild The ebuild for the new version. Builds fine, didn't have time to test "debug" USE...
Created attachment 85344 [details, diff] build.patch Patch for f..ked-up Windows backslashes...
Adding my vote to please have Nini bumped to 1.1.0 in portage. This release has been out for some time, and is stable. I can't see any reason for the delay. (I'm not sure what the discussion of whether this belongs in portage is about. This is a useful and well-written/maintained development library - whether or not something depends on it shouldn't affect it being in the tree.)
Added to portage. The new version compiles for the .NET 2.0, (uses mono-2.0). The build is still not perfect though (which is the reason for the delay).
