Ebuild for libmxp (MUD eXtension Protocol). Currently only used by games-misc/kmuddy. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 61858 [details] libmxp-0.2.2.ebuild
I'll assume you meant games-mud/kmuddy. Is it optionally or is it a required dep for newer versions?
Yes of course, I meant games-mud/kmuddy and its an optional. If present the library will be autodetected by the configure script of kmuddy.
(In reply to comment #3) > If present the library will be autodetected by the configure script of kmuddy. Ouch. Got a patch to add an --enable option for it? We don't allow things to use autodetection like that, as it breaks the dependency tree of portage.
(In reply to comment #4) > Got a patch to add an --enable option for it? We don't allow things to use > autodetection like that, as it breaks the dependency tree of portage. Got it. I hope using a new local USE flag (for kmuddy) is the right way to implement it. I also didn't know what category the libmxp ebuild will end up. Locally I put it in games-misc. If thats not correct the DEPEND in the patch for kmuddy will have to be corrected.
Created attachment 62188 [details, diff] Patch for kmuddy to add --with-mxp option to configure
Looks like upstream has disappeared.