URL:
<http://gna.org/patch/?6883>
Summary: Control of files created by Qt libraries vs freeciv
storage directory
Project: Freeciv
Submitted by: cazfi
Submitted on: Sun 31 Jan 2016 03:32:19 PM EET
Category: client-qt
Priority: 5 - Normal
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Planned Release: 3.0.0
_______________________________________________________
Details:
From bug #24359:
"In TRUNK we may later want to use 'freeciv storage dir' instead."
What should we do in regard to Qt framework written files in regard to
use-cases for which freeciv storage directory concept exist in TRUNK?
Consider these:
- Co-existence of freeciv and properly created forks; things like client
settings files (maybe having different set of options in forks and upstream
freeciv) are kept independently
- Possibility to set storage directory to writable location when home
directory is on read-only media (the reason I started to work on freeciv
storage directory concept was some bootable CD scenarios I am working on)
_______________________________________________________
Reply to this item at:
<http://gna.org/patch/?6883>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Freeciv-dev mailing list
[email protected]
https://mail.gna.org/listinfo/freeciv-dev
