I've been told that a lot of X-related utilities have been "~" keyworded out as part of the modular Xorg switchover, to see which ones are really used. One of the first things I needed to do after emerging modular X was to reset the font specs for xterm. And I need xfontsel in order to be able to pick a valid font. That required me to override the keyword before I could emerge it. Note, I'm only asking for myself (i.e. x86), but I wouldn't be surprised if other users on other architectures run into this issue as well.
*** Bug 140193 has been marked as a duplicate of this bug. ***
Nothing in the tree depends on this. If you think this is a dependency for something, you should file a bug for those ebuilds, meanwhile I don't see why this needs to be stable.
Does "stable" have to do with the utility of the application or the matureness/stability of the application ? I've been using xlsfonts and xfontsel ever since I started using linux about 8 years ago and it has been part of gentoo under xfree/xorg so why suddenly mark it unstable now ? It's an application in itself and I don't think any other app will depend on it even.
Don't listen to Jakub. =) If you use something that was previously stable, it oughta get stabled.
Comment #2 > Nothing in the tree depends on this. If you think this is a > dependency for something, you should file a bug for those > ebuilds, meanwhile I don't see why this needs to be stable. This is a necessary application. One example... xterm seems to have defaults that work great on a 640x480 display. On my 1600x1200 display, xterm defaults to microscopic unreadable fonts. Having to {CTRL-RIGHT-CLICK} each time I open xterm is a pain. I need to enter a decent value in resources or as part of the xterm launch commandline. To do that, I have to find a valid existing font in a specific characterset, etc. xfontsel is the app that does it. The fact that mutt isn't a dependancy for other apps doesn't imply that mutt should be marked unstable.
Fixed, thanks!
