On Sun, 13 Dec 2009, patrick keshishian wrote: > This is a simple update to the the port to remove a fonts.alias entry > that is causing -current xenocara to not load the font. I posted about > this on ports@ a few days ago[0], but did not receive any response to > my question as to whether or not the new behavior was correct. > Regardless, it hardly makes sense to have an alias that is exactly the > same as what it is supposed to be an alias of.
I have nothing against that diff but I do wonder why it worked before and it doesn't anymore. Were we just lucky or did something change? I'd rather find the exact cause of this instead of using band-aid, and what about the other fonts ports? -- Antoine
