[MacPorts] #61743: mame: improve user experience when running
MacPorts
noreply at macports.org
Sun Dec 6 03:45:29 UTC 2020
#61743: mame: improve user experience when running
--------------------------+----------------------
Reporter: mascguy | Owner: mascguy
Type: enhancement | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: mame |
--------------------------+----------------------
Description changed by mascguy:
Old description:
> Presently, when launching Mame, the user is presented with several
> warnings:
>
> {{{
> $ mame
> Unable to create history.db
>
> Unable to create history.db
> }}}
>
> This is due to the default Mame configuration, which references read-only
> directories within the MacPorts tree.
>
> For the next port release, we should improve on this:
> * At a minimum, the port notes should mention that a custom user
> configuration file (.ini) will fix such issues.
> * In addition, it would be helpful to provide an example user
> configuration file.
> * And finally, it might also be worth using a default configuration, that
> references user-writable areas. Say, ~/Library/Application Support/Mame/
>
> Another consideration, is the Mame tools:
> * Currently, no soft links are created in ${prefix}/bin, for those
> additions.
> * For the next release, we should consider creating those... perhaps with
> a variant option to enable/disable.
> * To avoid possible clashes, consider adding a 'mame-' prefix to said
> links. (But need to verify that no issues are caused by that. For
> example, if any tool invokes another... that could be problematic. Net-
> Net, more testing/verification/investigation needed beforehand.)
New description:
Presently, when launching Mame, the user is presented with several
warnings:
{{{
$ mame
Unable to create history.db
Unable to create history.db
}}}
This is due to the default Mame configuration, which references read-only
directories within the MacPorts tree.
For the next port release, we should improve on this:
* At a minimum, the port notes should mention that a custom user
configuration file (.ini) will fix such issues.
* In addition, it would be helpful to provide an example user
configuration file.
* And finally, it might also be worth using a default configuration, that
references user-writable areas. Say, ~/Library/Application Support/Mame/
Another consideration, is the Mame tools:
* Currently, no soft links are created in ${prefix}/bin, for those
additions.
* For the next release, we should consider creating those... perhaps with
a variant option to enable/disable.
* To avoid possible clashes, consider adding a 'mame-' prefix to said
links. (But need to verify that no issues are caused by that. For example,
if any tool invokes another... that could be problematic. Net-Net, more
testing/verification/investigation needed beforehand.)
* And finally, tools-specific man pages aren't being installed. That will
also be taken care of in the next port release.
--
--
Ticket URL: <https://trac.macports.org/ticket/61743#comment:4>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list