Why is the use flag "mono" still masked?

[wing]

Code: Select all

# 2005/01/12 - Benjamin Schindler <config@gentoo.org>
# Optional mono support will never work until we have a stable mono compiler
mono

The use.mask entry was made in January, the reasoning had solid ground then, but we've made huge strides since that time. With Mono 1.1.6 and 1.1.7, why is it still masked same reason gtk-sharp is masked for ~/amd64??

It's very annoying to have to go in and remove the use flag (I've successfully used it in every use="... mono ..." package I've tried, and admittedly I am ~amd64) manually after every emerge sync, is there a use.unmask or some such I can put in my /etc/portage?

[Evil Dark Archon]

the file is /etc/portage/profile/use.mask and to unmask a flag you add the use flag with a - in front of it for example

Code: Select all

-mono

will unmask the mono use flag.

[ziegs]

they should all compile, but things don't always run so perfectly. also, i find it better to compile certain things from cvs, mainly gtk-sharp and all those libs and monodevelop. just add the mono version you want to your packages.unmask.

muine and monodev aren't quite stable on amd64. neither is beagle, but they all run to varying degrees.

[latexer]

It was still use masked since mono-1.1.x was in package.mask, which meant all those apps with USE="mono" would be broken for amd64. I just finally got the p.mask of mono-1.1.x removed, so expect to see more ~amd64 keywords, and eventually the use.mask being removed (i don't have an amd64 myself, so i can't do the keywording)