<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div>Forwarding my own message to the list because my client failed to reply-to the list. I am embarrassed. Apologies to elektra@markus-raab! Begin forwarded message: </div><blockquote type="cite"><div>From: Chanslor Rosenthal <<a href="mailto:chanslor@icloud.com">chanslor@icloud.com</a>> Date: April 27, 2021 at 11:03:23 AM PDT To: <a href="mailto:elektra@markus-raab.org">elektra@markus-raab.org</a> Subject: Re: RCF: Basedir specification for non-Linux </div></blockquote><blockquote type="cite"><div>For what it's worth, I do not (frequently) port to Mac, but I *do* frequently develop for Linux on Mac. I work on an outdated MBP, test against my Debian server and Manjaro desktop, a newer Mac, and sometimes other Linux devices. I mention this because, when I do that, I almost always leave the spec unchanged *for user files*. Things don't get tricky until you arrive at executables. Things get *very* tricky when you arrive at executables. "Straight" Unix programs are, for the most part, where they are supposed to be, but desktop Mac programs work more like an AppImage and do not live anywhere nor have anything resembling a desktop entry. Special-casing it may be the only good solution. Some kind of parser would probably be the easiest solution, a companion package that locates Mac locations from FreeDesktop-specified paths and envvars. Just my two cents. Other people do much more intensive work porting full desktop apps and etc.</div></blockquote></body></html>