> From: Daniel Hughes [mailto:[email protected]] > > Lets say I want to use it > in my opensource project and that I want that project to be included > in the Ubuntu Repositories. To do that I need to get my project into > debian. So because NewtonSoft.Json is not available as a deb package > in debian I include the dll directly in my package. Then I submit my > package to the debian. > > Debian then rejects that package because it has a binary in it. How do > I know this? Because I tried it with widemargin for using moq (the > .net mocking library which is opensource but not packaged for debian)
You make a good point. I have never cared because I'm not interested in getting something into the official redhat/debian repos. It sounds like the two choices are to either distribute your product a different way, or ask the developers of that package to distribute that way. When you explain to them why you want it (as described above) it sounds completely reasonable, and they might just go along with it. I will note: Before posting my previous email, I specifically yum searched for json, to make sure I wouldn't stick my foot in my mouth about newtonsoft.json actually being included in the redhat & epel repos. I did not see it there, but I *did* see json libraries for just about every other language, perl, python, php, C, ruby, golang... I didn't search apt. _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
