Issue 1646: distinguish between local prefs and remote prefs in _darcs/prefs

Title	distinguish between local prefs and remote prefs in _darcs/prefs
Priority	feature	Status	given-up
Milestone		Resolved in
Superseder		Nosy List	darcs-devel, dmitry.kurochkin, kowey
Assigned To		Topics

Created on 2009-10-11.07:50:12 by kowey, last changed 2017-07-30.23:24:15 by gh.

msg8951 (view)

Author: kowey

Date: 2009-10-11.07:50:10

I've complained about this several times, yet I can't find a bug to go with it.

A big source of user confusion is that darcs users _darcs/prefs for three very
different things:

  remote prefs:
    - motd <-- this could also be useful for patch-taggers
    - email
  local prefs:
    - author
    - defaultrepo
    - defaults
    - sources
    - boring
    - binaries
  internal metadata:
    - prefs <-- used by setpref 

Since we can't do much about the remote prefs and the internal metadata for
reasons of backward compatibility, I propose that we create a separate
_darcs/localprefs directory and check there first.  It would mean that old
versions of darcs won't recognise the prefs, but I don't think it's serious
enough of a problem to warrant a format change.

History
Date	User	Action	Args
2009-10-11 07:50:12	kowey	create
2010-09-28 08:24:52	kowey	link	issue1960 superseder
2017-07-30 23:24:15	gh	set	status: needs-implementation -> given-up

Issue 1646 distinguish between local prefs and remote prefs in _darcs/prefs