On Mon, Nov 09, 2009 at 10:50:02 +1100, Trent W. Buck wrote: > > Instead, we want to use something I believe is called a 'forcing > > function' (*) to make users consciously aware that they're installing > > a third party plugin that isn't part of Darcs proper. The forcing > > function in question would be to require plugins to be specified in > > the user configuration, something like this: > > > > frobnicate /home/me/darcs-frobnicator.py > > show index /usr/local/bin/hashed-storage-show-index > > show authors /usr/local/bin/darcs-show-authors > > delta-debug /usr/local/bin/even-better-than-bisect
> Mercurial has this, and what happened was the Debian packager turned > them (all?) on by default in /etc (i.e. the system-wide defaults). Hm, > that decision seems to have been reversed in current versions... This sort of confusion between defaults chosen by the packager and the actual system is why I'm secretly hoping that we never implement system-wide defaults. That's probably me being silly; we could probably just as easily strongly discourage packagers from enabling plugins. Besides, we may be forced to do it (system-wide defaults) because of the umask problem: http://bugs.darcs.net/issue1185 -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9
signature.asc
Description: Digital signature
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
