[fink:feature-requests] #245 Replacement/Update of ConfFiles

"K.-M. Schindler" <[email protected]>
Newsgroups gmane.os.apple.fink.tracker
Message-ID </p/fink/feature-requests/245/7938b0c1d0aafe82189acc29e287595eeeb5050e.feature-requests@fink.p.sourceforge.net>
OK. The dialogue after reinstall  sounds promising. It would also resolve the case, when a user has accidentally deleted a config file. No way to get it back, at least not intuitively. I am not sure, but the problem may be that dpkg still assumes that the file is present. Where would I have to check the sources for an implementation?


---

** [feature-requests:#245] Replacement/Update of ConfFiles**

**Status:** open
**Group:** 
**Created:** Sun Mar 05, 2017 03:04 PM UTC by K.-M. Schindler
**Last Updated:** Sun Mar 05, 2017 11:12 PM UTC
**Owner:** nobody


Files listed in the field ConfFiles do not get replaced in newer versions / revisions of a package. The only way is a purge, install sequence, which is a pain, when there is a large number of dependences. 
My suggestions is that with install or update there is a dialogue about which version to take similar to the one, when such a file has been changed manually, and with reinstall the file is replaced without dialogue.


---

Sent from sourceforge.net because [email protected] is subscribed to https://sourceforge.net/p/fink/feature-requests/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/fink/admin/feature-requests/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot

_______________________________________________
Fink-tracker mailing list
[email protected]
http://news.gmane.org/gmane.os.apple.fink.tracker
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.