Here is an update to the Mono project's latest release, as of 2 December 2003. Two patches have to be made in order to compile correctly. The ebuild has been updated to apply those patches before compiling. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 21703 [details] mono 0.29 ebulid file
Created attachment 21704 [details, diff] Patch to change location of 'monoresgen' utility
Created attachment 21705 [details, diff] Patch to comment out code that requires a non-existent key file. I don't know why, but this patch was added back in October: http://lists.ximian.com/archives/public/mono-patches/2003-October/024751.html but didn't make it into the final release for 0.29. The code would not compile on my system without this patch.
I have never submitted an ebuild before. Do I also need to submit the digest and Manifest files? All files attached can overlay the existing mono-0.28.ebuild, so the only changes needed are modifying the MD5 sums and file sizes in those files.
As nice as this ebuild is, we will not be putting mono 0.29 into portage until there is a cairo release. Cairo is now a dependency of mono's System.Drawing, and we refuse to support a cvs snapshot or a live cvs ebuild of Cairo. As well, this ebuild doesnt take into consideration the conditional of libicu, which should be a local use flag, turned on by default, or just forced on always. The non-existent key file is Reggie of ByteFX breaking the build again, there might or might not be a new release of the tarball that fixes this issue, so that patch might not end up being needed.
Will mono require X because of cairo ?
shouldnt, and you should still be able to get the system.drawing functionality you need.
I was able to compile the build without a Cairo CVS installed. Did I miss something?
Yes, you were able to compile, however you have no System.Drawing. Now, we will not be shipping an incomplete solution, as System.Drawing is a very important piece of the mono.
*** Bug 35093 has been marked as a duplicate of this bug. ***
*** Bug 35618 has been marked as a duplicate of this bug. ***
*** Bug 36715 has been marked as a duplicate of this bug. ***
*** Bug 38215 has been marked as a duplicate of this bug. ***
Thanks for the ebuild/diffs Shawn; it works fine. It is too bad they refuse to add this to gentoo. I think a better solution would be to add it and then mask it explaining why it is masked. 0.30 is almost out...
Sorry. But System.Drawing sounds like java.awt.* or javax.swing.* in the Java world. Not having a GUI would also cause the java application to crash. I have several C# programs here, and non needs System.Drawing? So at least for some code, this makes no difference. My point is that it still could be added, but should be masked ~ARCH. And the dependencies should either be soft, when they are not ultimatly needed, or hard when they are needed.
I want to use mono only for web pages and command line tools and don't care about the drawing package. Not having this as a masked ebuild just makes it more complicated for end-users. Add a friggin einfo warning to the masked ebuild, but don't just leave it out.
+1 for the previous poster's suggestion.
*** Bug 39390 has been marked as a duplicate of this bug. ***
Todd, I think you're being unreasonable! As others said, add it masked but don't just leave it out! I don't care about System.Drawing either!
Mono 0.30 is released. http://www.go-mono.com/archive/mono-0.30.html And it says it needs theese libs: Cairo 0.1.17 : http://www.cairographics.org/snapshots/ ICU 2.6.1 : http://oss.software.ibm.com/icu/download/2.6.1/index.html And more, but they are linked to from the releasenotes page. Good Luck! :)
Created attachment 24957 [details] A somewhat working ebuilds to merge cairo These ebuilds for cairo worked on my computer with a small modification (see bug #40400)
