Mrxvt is now working on releasing a UTF8 version. The current UTF-8 branch is alpha, and under heavy development, thus no package will be released for some time. I attach a live ebuild for the UTF8 branch, which can gracefully co-exist with the (stable) 0.5.4 branch. I know that you don't usually include live ebuilds into the regular portage tree. I'm sending this anyway so that anyone wanting to test the UTF8 branch will find a ready to use ebuild. Also there's an off chance this might qualify as an exception, and you'll add it to the regular tree... :) GI
Created attachment 170507 [details] Live ebuild for the UTF8 branch of mrxvt
If it's direct mrxvt successor (will become main mrxvt at one point and all changes from main branch are merged into this one) then I don't see a reason for separate package and would opt for mrxvt-9999.ebuild. Opinion?
(In reply to comment #2) > If it's direct mrxvt successor (will become main mrxvt at one point and all > changes from main branch are merged into this one) then I don't see a reason > for separate package and would opt for mrxvt-9999.ebuild. Opinion? Yes, it should eventually become mrxvt once it's stable. But it's quite far away from that now, and no release exists yet. An mrxvt-9999 ebuild might just confuse users -- If they think they're just getting the bleeding edge SVN mrxvt, they're wrong. It's a highly alpha utf8 branch. I wrote the ebuild so it can coexist with the regular mrxvt (so users can test easily, and use the stable version one if they don't need utf8). GI
No recent changes in SVN repo (http://materm.svn.sourceforge.net/viewvc/materm/) for over a year. I'm closing this bug.
