Thien-Thi Nguyen <[EMAIL PROTECTED]> writes: > () Matthieu Moy <[EMAIL PROTECTED]> > () Mon, 11 Aug 2008 12:04:56 +0200 >
>> Sure. Do "make all install", frob ~/.emacs as directed in the README >> (and docs, and "make install" blurb, ideally), enjoy. Actually... > > What is "~/" here? The sysadmin's $HOME? The user's? > > Excellent question. The ~ stands for the user's home dir. Right above, you suggested putting stuff in ~/.emacs right after "make all install". I hope you don't suggest that the sysadmin edits the _user's_ .emacs ... > If you don't like to read documentation, that's your choice. I accept reading the documentation to learn _how to user_ a program. But documentation shouldn't be needed to _allow the program to work_. Honnestly, did you read the Firefox manual before launching it? > So, your vision of a sysadmin's work is to just run "make && make > install"?? To me, the role of the sysadmin installing something is > also to check that the program works (i.e. is correctly installed). > > Sometimes a sysadmin has too much to do besides "make all install". > Sometimes a sysadmin doesn't know what is "correct" (for you). > Sometimes a sysadmin doesn't know what is "correct" (for anyone). > Sometimes a sysadmin doesn't know anything! (Or worse, doesn't care.) > Sometimes a sysadmin knows all and DTRT, now, but the system changes. Well, clearly, we don't have the same notion of what a good sysadmin is. But what you don't understand is the difference between _asking_ the sysadmin to do something, and _requiring_ him to do so. > > the user will have to override it anyway. > > Why the hell would he have to? > > Give me just one case where a FreeBSD user would have to > override the value given by the configure script of the package. > > Here are four cases: > The dvc-site.el-chosen diff is buggy. It is not in the FreeBSD package. > The dvc-site.el-chosen diff points to a file that is no longer > there. It does not in the FreeBSD package. > The dvc-site.el-chosen diff points to a file that is old (newer is > better). Then you have to give me a senario where someone would use the package manager to manage DVC, and would install diff by hand somewhere else. I can't find any. > The user requires a different diff per project. Really? Why would he do so? (and how would you do that anyway?) Now, none of your senarios are credible in the cases of the FreeBSD package, and you still claimed that "the user will have to override it _anyway_.". > There, you said it. It is THE SAME. So, why have it, Because it's an additionnal feature that takes around 20 lines of code in DVC and that solves 99% of the problems. Simple solution to simple problems. > A compromise (and more idiomatic) approach would be to mention in > the documentation (which configure could noisily hint at, upon > completion) that the sysadmin can create/edit site-start.el to add > the (setq ...) forms, in the same manner that users would, in their > personal customization file. See: (info "(elisp) Init File"). And what simple solution do you have for the FreeBSD package? (actually, it seems the package wasn't ported to DVC, but the Xtla port is still there) (up to now, I didn't see a senario where dvc-site.el would be harmfull, just cases where it's not useful) -- Matthieu _______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
