Opened 6 months ago
Last modified 6 months ago
#70020 assigned defect
2048.cpp does not remove its data folder upon deactivation
Reported by: | barracuda156 | Owned by: | chenguokai (Xim) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.9.3 |
Keywords: | Cc: | ||
Port: | 2048.cpp |
Description
Deactivating 2048.cpp
does not remove /opt/local/var/2048.cpp
folder and its contents.
Change History (3)
comment:1 follow-up: 2 Changed 6 months ago by ryandesign (Ryan Carsten Schmidt)
comment:2 Changed 6 months ago by barracuda156
Replying to ryandesign:
That's intentional. That's where high scores are kept. You would not want your high score list wiped out every time you upgrade the port.
Ok, fair enough. It would be removed if the port is uninstalled though?
comment:3 Changed 6 months ago by ryandesign (Ryan Carsten Schmidt)
MacPorts does not distinguish between removing a port due to uninstalling and removing it due to upgrading to a new version. To MacPorts, both are "deactivating".
It's the same situation as a database server (MySQL, PostgreSQL); you wouldn't want your databases or log files, which are stored in ${prefix}/var, to be wiped out for you when you upgrade or uninstall. Same with configuration files stored in ${prefix}/etc; you wouldn't want them reset to defaults when you upgrade or uninstall. These files, and any others not included in a port's destroot, intentionally remain untouched by MacPorts when you upgrade or uninstall ports.
That's intentional. That's where high scores are kept. You would not want your high score list wiped out every time you upgrade the port.