mono-1.0.1-r2.ebuild depends on >=dev-libs/icu-2.6.1, but laster upstream is 2.6, and only 2.[46] are in portage. DEPEND="virtual/libc >=dev-libs/glib-2.0 >=dev-libs/icu-2.6.1 ... Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 39842 [details, diff] Simple (correct?) fix
The dep for mono really is 2.6.1 (from the configure script). We don't have 2.6.1 in portage, but we do have 2.8 (as of Feb 2004) so effectively it means people have to use 2.8 with mono. CCing pyrania@gentoo.org as he has done the latest bumps, and there's no metadata.xml for the package. Markus, is getting 2.6.1 into portage a problem? (for people that wan't to get the suggested ICU version?)
Sorry, bad use of english language there ;-) I'm still getting to grips with gentoo versioning/dep scanning.. Btw, icu-2.6 works well with mono, and iirc it's suggested/recommended on go-mono.com. Unless my proxy-cache is out of date, they still are. If that's for a reason (stableness, etc) would it be a problem to s/2.6.1/2.6/ instead of createing a .1 ebuild for icu and/or upp'ing the dep to 2.8?
Okay, i put 2.6.2 into portage a while back to help resolve this. I will be stabling this version prior to finally getting a stable mono-1.0.x soon. In the future I think i will make the ICU support optional, as upstream is tending to move *away* from ICU, due to some issues they are having with it (says Miguel on IRC). Resolving FIXED.
